Institutional tier
Proof of Reserves
Proof of Reserves is a game about what an exchange's proof of reserves really shows. You climb a Merkle sum tree from your own leaf, combining it with each sibling the proof gives you, and check the root. Then you compare on-chain assets with the published liabilities and call it: covered, short or not proven. Decrypt shows what it misses.
Free, with a verified email address. An account saves your progress, and floors and tiers open as you level up.
What it teaches
What a proof of reserves proves, and what it does not.
- How a Merkle sum tree lets you check your balance is included without seeing anyone else's. See proof of reserves.
- Why a negative account hidden in the tree can make everything "match" while hiding liabilities.
- What a snapshot cannot show: other debts, assets borrowed for the day, later withdrawals.
How a round plays
- Your statement gives your account id, your balance in USDT cents and a private nonce. Your leaf is the hash of "leaf|id|balance|nonce".
- Climb: each step hashes your node with the sibling the proof gives you, on its stated side, and adds the two sums.
- Verified only if your root equals the published root, hash and total, and no number in the proof is negative.
- Then the reserve ratio: on-chain assets divided by the published liabilities. Make the call: covered, short, or not proven. A run is 6 proofs.
How it is graded
Verification has one answer: verified, mismatch or negative. The ratio passes within one display unit at one decimal of a percent. The call is covered (verified and at least 100%), short (verified and below) or not proven (the proof failed, so the published total cannot be relied on). Tampered proofs change a balance, a sibling hash, a sibling sum, a side, or hide a negative account.
The honest note
A proof of reserves is a snapshot, not an audit. An exchange has paused withdrawals the day after its founder said publicly that its assets were fine. Keeping funds on any exchange means trusting it, whatever proof it publishes.