A custodial platform asks you to trust that it holds what it owes. Proof of reserves is how we let you check instead.
What we publish
- What we owe: every customer balance in our ledger, added up at one moment.
- What we hold: the balance of our wallets on-chain at that moment, by network, and the ratio between the two.
- A Merkle root: a single fingerprint that commits to every customer balance and to the total.
- Every snapshot we have published, including any we have withdrawn.
All of it is on the public proof of reserves page.
Checking your own balance
- Step 1: Sign in and open Proof of reserves in your dashboard.
- Step 2: It shows your balance as counted in the latest snapshot, and the proof that it is included.
- Step 3: Check the proof in your browser there, or download it and check it on the public page or with code of your own.
Your balance in a snapshot is everything you had with us at that moment: available, delegated, unbonding, rewards, withdrawals in progress and deposits being checked.
The tree is a Merkle sum tree: every step up it adds up the balances beneath it. So a valid proof shows not only that your balance is in the tree, but that it was counted in the published total. Each entry is salted, so nobody can work out anyone else's balance from what we publish.
What it does not prove
- Debts outside our ledger. The total is what we owe customers, not everything the company owes.
- Who controls the wallets, unless their addresses are published with the snapshot. When they are not, the holdings figure rests on our word.
- Anything after the snapshot. It is one moment; the next snapshot is the next checkpoint.
Figures on this page are read from the platform’s current settings. Your dashboard always shows the ones that apply to your account.