Proofs · 30 days
Assets per proof
Proof systemGroth16Circom · snarkjs · BN128
Enclave
Last proof
Proof cadence · network
Last 60 days · one cell per 6-hour window · hover for time
On timeLateMissedPending
On time99.17%119 of 120 windows
Late1published after 15 min
Missed0none in 30 days
Windows charted24060 days · all assets
CadenceEvery 6 hours · 00:30 · 06:30 · 12:30 · 18:30 UTC
Publication delay · median3 min 40 s after the window opens
Proof sizeGroth16 · 3 curve points · 256 bytes
Verification gas≈ 230k · Ethereum
Pipeline
How each proof is produced
1 · ReadCustodian APIs and on-chain balances, inside the enclave
2 · CommitSalted field hashes → Keccak256 and Poseidon Merkle roots
3 · AttestAWS Nitro attestation document binds the root to the enclave
4 · ProveGroth16 (Circom + snarkjs) proves reserves ≥ liabilities
5 · PublishRoot written on-chain as the maximum mintable supply
On-chain roots
Latest published
Keccak256 root—
Poseidon root—
ZK proof—
Proof ID—
Feed—
Enclave—
Attestation log
Latest published proof per asset
| Time (IST) | Asset | Reserves | Supply | Ratio | Merkle root | ZK proof | Proof ID | Status |
|---|
The API exposes the latest proof per asset. A historical attestation log needs a paginated proofs endpoint.
AFI outputs are not investment advice. Figures reflect the latest attested state; verify any value against the on-chain root.Data refreshes every 6 hours · Methodology ↗