Learn: plumbing
What does a proof of reserves actually prove?
A proof of reserves shows two things on one day: that customer balances, including yours, add up to a published total in a Merkle tree, and that the exchange controlled at least that much in assets. It cannot show other debts, assets borrowed for the snapshot, or what happened the day after.
How it works
When you leave crypto on an exchange, you hold a promise, not coins. The exchange keeps one pool of assets and a ledger of what it owes each customer. A proof of reserves tries to show that the pool covers the ledger. It has two halves: the liabilities (what customers are owed) and the assets (what the exchange holds on chain).
The liabilities half uses a Merkle sum tree. Each customer balance becomes a leaf: a hash of the account id, the balance and a private nonce. Pairs of nodes are hashed together, and each parent also carries the sum of its two children, up to a single root whose sum is the total owed. The exchange publishes the root. Each customer gets a short proof: the sibling nodes on the path from their leaf to the root. Rebuilding the root from your leaf and those siblings shows your balance was counted, without revealing anyone else's.
The assets half is usually a list of wallet addresses the exchange shows it controls, often by signing a message with their keys. Dividing assets by the published total gives the reserve ratio. Above 100%, the assets covered the claims on that day.
The exact rule the games grade by
The rule the games use: leaf = sha256("leaf|id|balance|nonce"); parent = sha256("node|left hash|left sum|right hash|right sum"), and its sum = left sum + right sum; odd levels are padded with a zero-sum node. A proof verifies only if your rebuilt root matches the published root in both hash and total, and no sum in the proof is negative. Reserve ratio = on-chain assets / published liabilities. A failed proof means the published total cannot be relied on, whatever the ratio says.
Step by step
- Compute your leaf from your own statement: account id, balance and nonce.
- Take the first sibling from the proof and hash the pair in the stated order, adding the two sums.
- Repeat with each sibling up the tree.
- Compare your result with the published root: the hash must match exactly, and so must the total.
- Check that no sum in your proof is negative. A negative account can shrink the total while your path still verifies.
- Divide the on-chain assets by the published total, and make the call: covered, short, or not proven.
Worked example
Your statement says account acct-3e55 holds 750.00 USDT, with nonce 0b93fa4c. Your leaf hash starts ca98de9f4a.
The proof has two steps. First, a sibling on the right with a sum of 4,800.00: hash the pair, and the parent sum is your balance plus 4,800.00. Second, a sibling on the left with a sum of 14,500.00: hash again and add.
The result matches the published root, which starts db1762a1a6, with a total of 20,050.00 USDT across 4 accounts. Your balance is counted, and no sum on your path is negative.
The exchange shows 18,900.00 USDT of assets on chain. The reserve ratio is 18,900.00 / 20,050.00 = 94.3%. The proof verifies, but the assets fall short of what customers are owed: the call is short.
Takeaway: A valid proof and a ratio of 94.3%: your balance is in the tree, and the tree is not fully covered. Both halves matter, and neither is an audit.
Common mistakes
- Reading assets without liabilities. A list of wallets holding a large amount says nothing on its own. What matters is assets against everything owed. A venue can show large reserves and still owe more.
- Not checking your own proof. The tree only protects customers who verify their leaf. If nobody checks, balances can be left out or shrunk without anyone noticing.
- Missing a negative account. A fake account with a negative balance placed next to yours lowers the published total while your hashes still match. Reject any proof with a negative sum.
- Treating one day as forever. A proof is a snapshot. Assets can be borrowed for the day and returned the next, and withdrawals after the snapshot are invisible.
What this does not tell you, and what can go wrong
A proof of reserves cannot see liabilities outside the tree: loans the exchange took, money owed to other firms, or customer claims it chose not to include. It cannot tell whether the on-chain assets were borrowed or are pledged elsewhere. It does not show whether the assets can be sold at full value in a hurry. A token the exchange issued itself, counted as an asset, is especially weak evidence.
The collapse of a large exchange in November 2022, with customer funds missing and its founder later convicted of fraud, is why the idea became popular, and it also shows its limits: a snapshot of wallets would not have revealed what was owed and to whom. An independent audit of the whole balance sheet covers far more than a proof of reserves. Keeping funds on any exchange means trusting it, whatever it publishes. See self-custody for the trade-off.
Questions people ask
What is a Merkle tree?
A structure that hashes data in pairs, level by level, until one root hash remains. Changing any leaf changes the root, so a short list of sibling hashes can prove that one leaf is included. A Merkle sum tree also carries a running total, so it proves the leaf is counted in the published sum.
Does proof of reserves mean an exchange is safe?
No. It shows assets and customer balances on one day. It does not show other debts, borrowed assets, or how the exchange is run. It is better than no evidence, and much weaker than a full audit. Some of the ways crypto platforms have failed, such as customer funds lent out to a related firm, are things a snapshot would not catch.
How do I verify my balance in a proof of reserves?
Use your account id, balance and nonce from the exchange to compute your leaf, then hash it with each sibling in the proof, on the stated side, adding the sums. Your final hash and total must match the published root. Practise it on simulated trees in the Proof of Reserves game.
What is a good reserve ratio?
At least 100% of customer liabilities, held in assets the exchange did not issue itself, verified by a proof that customers actually check. Even then, the ratio says nothing about debts outside the tree or about the day after the snapshot.
Practise it
Reading about a rule is not the same as applying it. These games generate a fresh simulation each round, ask you to make the call first, and grade you against the same rule.
Proof of Reserves
Verify your balance in a Merkle tree, then compare assets with liabilities. Decrypt shows what the proof misses.
The AuditorBoss
The final boss reads you five claims a venue makes about itself. Sign only what the evidence on screen shows.