Proof of Reserves
Understand crypto exchange proof of reserves, Merkle liability proofs, solvency limitations, encumbrances and practical due diligence.
Reading progress — saved on this device
Proof of reserves (PoR) is evidence intended to show that a custodian controls assets corresponding to some or all customer balances. Stronger designs pair on-chain asset evidence with a cryptographic commitment to customer liabilities.
Core concept
A useful reserve exercise asks two separate questions at the same point in time: what assets does the custodian control? and what amounts does it owe customers?
On-chain transparency can make asset-side evidence unusually visible compared with traditional finance. But the blockchain cannot automatically reveal off-chain debts, legal priorities, pledged assets or missing customer liabilities.
That is why the strongest interpretation of PoR is verifiable custody evidence inside a defined scope, rather than “the exchange is safe”.
Asset-side evidence
- Wallet ownership can be demonstrated through signed messages, controlled test transactions or independently verified custody records.
- Published addresses let observers confirm balances on-chain at a given block/time.
- Assets should be valued consistently, with illiquid self-issued tokens treated carefully.
- Methodology should address whether assets are borrowed, pledged, lent out or otherwise encumbered.
- Custody providers and omnibus structures can complicate direct wallet attribution.
Liability-side evidence
Publishing every customer's balance would create privacy problems. Merkle-tree structures can instead commit to a liability dataset while allowing each customer to verify that their own balance was included.
| Evidence | What it can show | What it cannot prove alone |
|---|---|---|
| Wallet proof | Control of on-chain assets | Complete liabilities |
| Merkle inclusion | Your balance appears in committed set | No omitted customers elsewhere |
| Coverage ratio | Assets vs included liabilities | Other debt/encumbrances |
| Independent assurance | Method/scope reviewed | Anything outside engagement scope |
Are customer liabilities complete across spot, margin, earn/lending and all legal entities?
Are reserve assets available to customers or subject to prior claims?
Worked example
An exchange demonstrates £1.05bn of reserve assets against £1.00bn of included customer liabilities: apparent coverage 105%.
That sounds strong. But suppose £300m of the reserve assets secure a separate loan with priority claims. The simple PoR coverage ratio no longer proves customers are fully protected. Alternatively, if an “earn” product's liabilities were excluded from the £1.00bn denominator, the ratio would also be incomplete.
The reverse issue matters too: an exchange can be solvent even if a simple wallet snapshot appears temporarily below liabilities because some assets are with qualified custodians or banks not represented by the visible address set. Scope must be read before interpreting the number.
Common mistakes and misunderstandings
- Calling wallet ownership proof a complete financial audit.
- Ignoring customer liabilities and focusing only on reserve addresses.
- Assuming a Merkle inclusion proof validates the completeness of all liabilities.
- Ignoring pledged/borrowed/encumbered reserve assets.
- Treating a point-in-time snapshot as continuous solvency assurance.
Knowledge checkpoint
- Why can 105% reserve coverage still coexist with insolvency or customer shortfall risk?
- What does your Merkle inclusion proof establish, and what does it not establish?
- Why should assets and liabilities be measured at the same time?
- Which product or entity exclusions would you specifically look for in a PoR report?
FAQ
❓ Is PoR a full audit?
Usually not by itself. Scope and assurance standards vary.
❓ What is a Merkle tree used for?
It can support privacy-preserving verification that a balance was included in a committed dataset.
❓ Does PoR prove assets are unencumbered?
No, unless encumbrance is specifically addressed.
❓ Is more frequent PoR better?
It improves timeliness, but does not fix incomplete methodology.
Summary
- Proof of reserves provides evidence about custody assets and sometimes customer liabilities.
- Wallet balances alone do not prove solvency.
- Liability completeness, encumbrances, scope and timing are essential.
- PoR is strongest as one component of exchange due diligence.
This building block is educational and not a trade recommendation.
Want this in a personalised order?
Take the crypto assessment and get a custom path of 10 modules matched to what you already know. Free, no card required.
Build my path →