Reserves, proven on-chain.
connecting…
A zero-knowledge proof that the vault's reserves fully back what depositors are owed — read live from the chain, at market value (not stress- or liquidation-adjusted). Don't trust this page; read the contract.
Latest attestation
reading registry…
Trust stack
Trustless
zkVM proof · SP1
The coverage computation runs in the SP1 zkVM and is verified on-chain. Even the operator can't forge the "covered" verdict.
Trusted · TCB
zkTLS attestation
Balances are attested over TLS by the Primus attestor — a trusted attestation layer, the one non-ZK link in the chain.
◇ Audit
Pending · gate
Circuit audit
An independent audit of the proof circuit is scheduled ahead of mainnet — the final gate.
Proves
- Attested reserves exist and cover on-chain liabilities at market value, at the proof's timestamp.
- The coverage math ran honestly — zkVM-verified on-chain — against the vault's own reported liability.
- No double-counting across the attested accounts.
Does not prove
- Not stress-adjusted. Mark-to-market — not survival of a crash, forced liquidation, or conversion cost.
- Attestor-dependent. Balances enter via a named attestor (TCB); the liability anchor is operator-reported.
- Doesn't rule out a borrowed-for-snapshot balance, or prove reserves are unencumbered.
- Point-in-time. Coverage at T says nothing about T+1.
Don't take our word for it — the proof is a zero-knowledge proof checked by an on-chain verifier, and every artifact below is public. Read the chain, match the circuit, re-run the verification.
…