Six primary checks. All public.
The demo is backed by deployed bytecode, finalized transactions, an XRPL payment and a Google-signed Confidential Space attestation. Open any card and verify it without trusting this website.
Signature generated inside GCP Confidential Space; the exact image digest is bound by a Google token, then accepted on Coston2.
open record transaction ↗Full prepare, FdcHub, Relay, DA-layer and verify flow. The approved source commitment must match the enclave claim.
open FDC-backed record ↗A real XRPL testnet challenge payment proves control of the registered reserve address, with replay and freshness checks.
open Coston2 proof ↗A commitment reveal proves insolvency, revokes the attestation and slashes recorder plus endorsers to the challenger.
open slash transaction ↗Source-verified sender bound to FlareTeeManager public extension 66194, with EVM key type and encrypted instruction routing.
inspect verified adapter ↗Inspect the XRP sender, receiver, amount and challenge memo on XRPL itself—the Flare proof points back to this transaction.
open on XRPL testnet ↗One record, two independent proofs
Every attestation must clear all five stages. Watch them light up as a proof runs — the same spine drives the honest path and the fraud path below.
Prove solvency confidential
Feed the enclave your figures. Only a signed commitment and an FDC reserve proof reach the chain — the raw numbers stay with you. Runs live on Coston2 (~2 min for one FDC round).
Issuer input private
Subject is the FXRP agent vault whose solvency you're asserting.
Commitment builder on-chain hash
This reproduces, in your browser, the keccak256(abi.encode(…)) the verifier computes on-chain. It's proof that the chain only ever stores a hash.
▲ Stays private
Inside the enclave · never transmitted
◆ Goes on-chain
The only thing the world sees
Change any figure or the salt and both hashes change completely — yet neither can be reversed back to the numbers. The live proof above uses a fresh CSPRNG salt generated inside the enclave.
Live trace
Real orchestration: enclave signature → FDC round-trip → recordSolvency on Coston2.
Verify without numbers public
Anyone can confirm "solvent at T" straight from the chain. Paste an attestation id — you'll see the exact registry record and nothing more. No reserves. No liabilities.
Lie, and lose the stake accountable
Privacy without accountability is just a secret. Here a malicious attestor signs "solvent" over figures that are actually insolvent, records it — then anyone reveals the committed figures and slashes the stake.
The fraud
Reserves < liabilities, but signed solvent = true.
Stake at risk
The attestor's bonded collateral, before and after the slash.
Many stakes, one claim quorum
An issuer can demand that independent staked attestors co-sign an attestation before it counts as final. Every endorser puts their own bond behind the same claim — and is slashed with the recorder if it is ever proven false. Endorse from your own wallet, or let the service's second attestor do it.
Your attestor wallet MetaMask · Coston2
Checking for a browser wallet…
Endorsing locks your stake for the claim's challenge window. If the claim is proven fraudulent, you are slashed alongside the recording attestor — only endorse what you have re-verified.
Why quorum matters
Attestation history
Every attestation recorded by this deployment, straight from on-chain events — commitments only.
| id | subject | attestor | at T | status | endorsements | tx |
|---|
XRPL-native reserve proof FDC Payment
Reserves for FXRP agents live on the XRP Ledger. Alongside the Web2Json amount proof, a subject proves it controls its registered XRP reserve address: it answers a contract-derived challenge with a 1-drop XRPL payment whose memo carries the challenge reference, FDC attests the payment, and XrplReserveProof.proveControl verifies everything on-chain — no custodian API in the loop.
Two Flare rails, one guarantee
Neither bounty is decorative: recordSolvency reverts unless it receives both a valid enclave signature and a valid FDC proof from the subject's approved source.
confidential The enclave
The solvency check and every sensitive figure run inside a TEE extension. It emits a domain-separated EIP-191 signature over the commitment; the verifier recovers the signer on-chain and requires it to equal the registered enclave address — the FCC settlement pattern.
interoperable The data + asset rails
An FDC Web2Json proof brings the off-chain reserves on-chain through the full round-trip (prepare → FdcHub → Relay → DA-layer → verify). The subject is bound to a real FXRP agent vault, and an FDC Payment proof adds an XRPL-native reserve-address control check — all resolved via FlareContractRegistry, no hardcoded addresses.
Honest scope shipped vs remaining
✓ Shipped and verifiable
Explorer + Google attestation evidence today
◐ FCC production handoff
Precisely separated from completed evidence