Proof of reserves
Trust, made verifiable.
Transparency is not a promise. It is a process. Explore asset backing and how inclusion proofs work.
Illustrative platform reserves · live USD valuation
$8,419,000,000
Snapshot: June 30, 2026 • Six covered assets
At least 1:1 backing
Every covered asset has a modeled reserve ratio above 100%.
Asset-by-asset coverage
BTC104%- User liabilities
- 125,000
- Platform reserves
- 130,000
Amounts in BTC · reserves ÷ liabilities
ETH102%- User liabilities
- 1,450,000
- Platform reserves
- 1,479,000
Amounts in ETH · reserves ÷ liabilities
USDT101%- User liabilities
- 6,500,000,000
- Platform reserves
- 6,565,000,000
Amounts in USDT · reserves ÷ liabilities
USDC103%- User liabilities
- 1,800,000,000
- Platform reserves
- 1,854,000,000
Amounts in USDC · reserves ÷ liabilities
SOL105%- User liabilities
- 8,500,000
- Platform reserves
- 8,925,000
Amounts in SOL · reserves ÷ liabilities
XRP102%- User liabilities
- 650,000,000
- Platform reserves
- 663,000,000
Amounts in XRP · reserves ÷ liabilities
A record of transparency
Illustrative monthly reserves • USD billions • not historical market valuations
Small proofs. A bigger picture.
How a Merkle tree works
A snapshot converts account balances into hashed leaves. Pairs of hashes are combined until one root represents the entire dataset. A short path of sibling hashes lets you check that a leaf belongs to that root without exposing other accounts.
Inclusion alone does not prove ownership of reserves, completeness of liabilities or freedom from encumbrances. A real assessment also needs independently checked balances and custody evidence.
Verify my assets
Snapshot archive
| Snapshot date | Assets | Method | Report |
|---|---|---|---|
| June 30, 2026 | 6 assets | Merkle tree • Demo | |
| May 31, 2026 | 6 assets | Merkle tree • Demo | |
| April 30, 2026 | 6 assets | Merkle tree • Demo | |
| March 31, 2026 | 6 assets | Merkle tree • Demo |