Crypto · Wallets, exchanges and custody
Proof of reserves: what an exchange audit does and does not show
How a crypto exchange proves it holds customer coins with a Merkle tree, worked through on eight balances with real hashes, and why that still falls short of an audit.
On this page
A crypto exchange's customers see balances on a screen. They cannot see whether the exchange actually holds the coins behind those balances. A proof of reserves is an attempt to close that gap: the exchange shows, with cryptography and usually an outside accountant, that on a given date it controlled at least as many coins as it owed its customers.
The idea spread after several large platforms failed in 2022 with far fewer assets than their customers' balances implied. It is a real improvement on showing nothing. It is also much narrower than the word "proof" suggests, and narrower still than an audit.
This lesson builds a small proof of reserves by hand, with real hashes, so you can see what a customer is able to check. Then it sets out what the method cannot tell you. It is not a judgment on any exchange.
The problem it tries to solve
When you deposit coins at an exchange, they go into wallets the exchange controls, and your account is credited in the exchange's own database. Crypto exchanges vs self-custody explains that arrangement. The balance is a promise. An exchange that lends, loses or spends customer coins can go on displaying the same balances until the day withdrawals stop.
A bank or broker faces the same temptation, and the answer there is regulation: capital rules, segregation of client assets, examinations and audited accounts. Much of the crypto exchange business grew up outside those rules. Blockchains offer one thing traditional finance does not: anyone can see what any address holds. A proof of reserves tries to use that openness in place of some of the missing oversight.
It needs two halves:
- Assets. Show that the exchange controls addresses holding X coins.
- Liabilities. Show that customer balances add up to Y, in a way customers can test.
If X is at least Y for each coin, the exchange is said to be fully reserved for that coin on that date.
The asset side: proving control
Balances on a blockchain are public, so the exchange only has to show that certain addresses are its own. It does that by signing a message with each address's private key, or by moving a specified amount at a specified time. An accountant, or anyone, can then add up what those addresses hold.
This half is the simpler one, with two soft spots. Control is not ownership: coins borrowed from a lender or an affiliate for a few days sit in the exchange's addresses just the same. And control at one moment says nothing about the next.
The liability side: a Merkle tree
The harder half is the list of customer balances. The exchange cannot publish it, for privacy and commercial reasons, and customers have no reason to trust a bare total. The standard answer is a Merkle tree, a structure built from hashes.
A hash function turns any data into a short fingerprint. SHA-256, the function bitcoin uses, produces 64 hexadecimal characters, and changing one digit of the input produces a completely different output. How a blockchain works covers hashes in more detail.
To build the tree:
- Hash each customer's record (an identifier and a balance). These are the leaves.
- Pair the leaves and hash each pair together to make a parent.
- Repeat, level by level, until one hash is left: the Merkle root.
In the sum tree variant used for liabilities, each parent also records the total of the balances beneath it and includes that total in its hash. The root then commits to two things at once: every individual balance, and their sum.
A worked example with real hashes
Eight invented customers, A to H, hold 0.5, 2, 1.25, 0.1, 3.4, 0.75, 0.02 and 1.98 BTC: 10 BTC in all. The figure was computed with SHA-256; it shows the first 8 characters of each hash.
The exchange publishes one line: root 3f747141…, total 10 BTC. An accountant confirms
that the exchange's addresses hold at least 10 BTC.
Customer C wants to know whether their 1.25 BTC is inside that total. The exchange gives C three values, the siblings along C's path. C then does the arithmetic alone:
| Step | C combines | Result |
|---|---|---|
| 1 | Own record: C, 1.25 BTC | Leaf hash 7542b856… |
| 2 | Own leaf + sibling D (0.1, 2ce6e852…) |
CD: 1.35 BTC, 176c28a8… |
| 3 | CD + sibling AB (2.5, 53f21af6…) |
ABCD: 3.85 BTC, e5f913d6… |
| 4 | ABCD + sibling EFGH (6.15, 6cb316c7…) |
Root: 10 BTC, 3f747141… |
The result matches the published root, so C's balance was included, and the totals along the way add up to the published 10 BTC. C learned no other customer's balance, only subtotals.
Now suppose the exchange had wanted to shrink its liabilities by recording E's 3.4 BTC as
0.4. The total would fall to 7 BTC and the root would become 0b1af02c…, a different value
entirely. C's check would still pass, because C's side of the tree is untouched. Only E can
catch the change, and only by running the check.
That is the method's central property and its central weakness in one example. Each customer can verify their own inclusion cheaply. Nobody verifies anyone else's.
How big is a proof?
The number of sibling values a customer needs equals the number of levels in the tree, which grows very slowly.
proof length = log2(number of accounts), rounded up
8 accounts → 3 values
1,000,000 accounts → 20 values
100,000,000 accounts → 27 values
This is why the scheme scales to very large exchanges: a customer's check is always a few dozen hashes.
What a proof of reserves does not show
Other liabilities. The tree lists customer balances. It does not list bank loans, amounts owed to trading partners, tax bills or claims by affiliated companies. An exchange can hold 104% of customer balances and still be insolvent once its other debts are counted.
Borrowed or encumbered assets. Coins in the exchange's addresses on snapshot day may have been borrowed for the purpose or pledged as collateral elsewhere. One exchange that publishes these reports says so directly in its own description of the method: the procedure cannot identify hidden encumbrances, and it proves control of funds only at the point in time of the review.
Omitted accounts. A balance left out of the tree, or understated, is caught only if that customer checks. An account whose owner never looks is an account that can be quietly dropped, so the protection is only as wide as the share of customers who verify. A sum tree also needs a rule against negative balances, since one fictitious negative account would cancel real liabilities; verifying that for the whole tree requires either trusting the accountant or more advanced cryptography.
Everything after the date. The report describes one moment. The coins can leave the next morning.
The firm's own token. Reserves are counted coin by coin. If part of an exchange's "assets" is a token the exchange itself issued, its value depends on the exchange's survival, which is the thing in question.
It is not an audit. In March 2023 the Public Company Accounting Oversight Board, which oversees auditors of US public companies, issued an investor advisory titled "Exercise Caution With Third-Party Verification/Proof of Reserve Reports". Its points: these engagements are not audits, they are not performed under the board's auditing standards or subject to its inspection, and they do not provide meaningful assurance about whether a firm has enough assets to meet its obligations. A proof-of-reserves report from an accounting firm is a narrow agreed procedure, not an opinion on financial statements.
Reading a proof-of-reserves report
Questions worth asking of any such report. None of them has a reassuring default answer.
- Who did the work, and under what kind of engagement? An audit, an attestation and an "agreed-upon procedures" report give very different levels of assurance.
- What date does it cover, and how often is it repeated? A yearly snapshot leaves 364 days unobserved.
- Does it cover liabilities, or only assets? A list of wallet balances without a customer-liability tree is half a proof.
- Which coins and which entities? Groups of companies can move assets between affiliates. A report on one entity says nothing about the others.
- Can you verify your own balance, and have you?
- Are the exchange's own tokens counted as reserves?
Proof of reserves compared with other assurances
| Assurance | Covers assets | Covers all liabilities | Period | Who stands behind it |
|---|---|---|---|---|
| Proof of reserves (Merkle tree) | Yes | Customer balances only | One date | The exchange; an accountant's procedure |
| Audited financial statements | Yes | Yes | A full year | An auditor, under auditing standards |
| Regulated custody and segregation | Yes | By rule | Continuous | A regulator's rules and examinations |
| Self-custody | Not needed | Not needed | Continuous | You, by holding the keys |
The table explains why a proof of reserves is best read as one piece of evidence. Audited accounts cover the liabilities it misses, and regulation covers the days between snapshots. Self-custody removes the question and replaces it with the risks described in Hot wallets vs cold wallets.
Pitfalls
- Treating "100% reserved" as "safe". The phrase describes one ratio on one date.
- Trusting the badge, not the check. The cryptography protects only customers who use it. A proof nobody verifies is a press release.
- Confusing reserves with insurance. A fully reserved exchange can still be hacked, frozen by a court or stopped by an operational failure. Coins held at an exchange are not covered by SIPC or FDIC insurance, and losses can be total.
- Ignoring the corporate structure. Customers contract with a specific legal entity. Reserves shown for a different one are not theirs to claim.
How Finabase does it
Finabase is not an exchange and holds no customer coins, so it has no reserves to prove. It also does not rate exchanges or publish their reserve reports. Its role with crypto is prices: the crypto list and quote pages such as BTC.X show market data.
One practical link to this lesson: a reserve report states holdings in coins, and their dollar value moves with the market every day. A reserve "worth $1 billion" on the snapshot date is worth whatever the coins fetch later, which a price chart will show and the report will not. The tree in this lesson is a Finabase calculation over invented balances, built to be small enough to follow by hand.
Frequently asked questions
Does proof of reserves mean an exchange is safe?
No. It shows that on one date the exchange controlled at least as many coins as the customer balances it disclosed. It does not cover the exchange's other debts, borrowed assets or anything that happened afterward.
Is a proof of reserves the same as an audit?
No. An audit examines a company's full financial statements, including all liabilities, under professional standards. The PCAOB told investors in March 2023 that proof-of-reserve reports are not audits and do not provide meaningful assurance about a firm's ability to meet its obligations.
How do I verify my own balance in a proof of reserves?
The exchange gives you your record's hash and the sibling hashes on your path. You hash your record, combine it step by step with the siblings, and compare the result with the published Merkle root. Exchanges that offer this usually provide instructions or open-source code.
What is a Merkle root?
It is the single hash at the top of a Merkle tree. Because every hash depends on the ones below it, the root is a fingerprint of the whole set of balances: change any one and the root changes.
Could an exchange fake a proof of reserves?
It could not fake an individual customer's inclusion without that customer being able to detect it. It could omit or understate accounts whose owners do not check, borrow coins for the snapshot, or leave out non-customer debts. Those gaps are why the method is limited.
Summary
A proof of reserves compares the coins an exchange controls with the coins it owes customers on a single date. The asset side rests on showing control of blockchain addresses, and the liability side on a Merkle sum tree, which lets each customer confirm with about twenty hashes that their balance is inside the published total. The worked example shows both the strength and the hole: a customer can prove their own inclusion and nothing about anyone else's. The method leaves out other liabilities, borrowed assets and every day but the snapshot, and the PCAOB has warned that these reports are not audits. Read one as a single piece of evidence about a firm, never as a guarantee that money held there cannot be lost.
Check your understanding
5 questions on this lesson. Each answer comes with the reason, and nothing is scored.
An exchange publishes a Merkle root and a total of customer balances. What can an individual customer verify with their own proof?
- That every customer’s balance is correct
- That their own balance is included in the published total
- That the exchange has no other debts
Show the answer
B. That their own balance is included in the published total The proof recomputes the root from the customer’s own record and the sibling values. It confirms that one record was counted, and says nothing about the others.
In the worked example, the exchange records customer E’s 3.4 BTC as 0.4 BTC. Customer C runs their check. What happens?
- C’s check fails, exposing the change
- C’s check passes against the new root; only E could detect the change
- The Merkle root stays the same
Show the answer
B. C’s check passes against the new root; only E could detect the change The root changes, but the exchange publishes the new one and C’s side of the tree still hashes to it. A misstated account is caught only if its owner verifies.
An exchange shows reserves equal to 104% of customer balances. Why might it still be insolvent?
- Because the proof covers customer balances but not loans and other liabilities
- Because 104% is below the legal minimum
- Because Merkle trees cannot count above 100%
Show the answer
A. Because the proof covers customer balances but not loans and other liabilities Solvency is assets minus all liabilities. The tree lists only what is owed to customers, so debts to lenders, partners or affiliates sit outside it.
Why does a proof for an exchange with 1,000,000 accounts need only about 20 values?
- Because only 20 accounts are sampled
- Because a customer needs one sibling per level of the tree, and the number of levels is log2 of the accounts
- Because hashes are 20 characters long
Show the answer
B. Because a customer needs one sibling per level of the tree, and the number of levels is log2 of the accounts Each level halves the number of nodes, so a million leaves take about 20 levels. The customer needs the sibling at each level to climb to the root.
How does a proof-of-reserves report differ from an audit of financial statements?
- It is the same thing under a different name
- It is stricter, because it uses cryptography
- It is a narrow procedure on one date that does not examine all liabilities or follow auditing standards
Show the answer
C. It is a narrow procedure on one date that does not examine all liabilities or follow auditing standards The PCAOB warned in 2023 that these reports are not audits and give no meaningful assurance that a firm can meet its obligations. An audit covers the full accounts over a period.
Sources and further reading
- Kraken — Proof of Reserves (method, Merkle tree, and the shortcomings the exchange itself lists)
- PCAOB — Investor Advisory: Exercise Caution With Third-Party Verification/Proof of Reserve Reports (March 8, 2023)
- SEC Office of Investor Education and Assistance — Crypto Asset Custody Basics for Retail Investors (Investor Bulletin, December 12, 2025)
- NIST FIPS 180-4 — Secure Hash Standard (SHA-256)
- Finabase calculation — a Merkle sum tree over eight invented balances, hashed with SHA-256 in the figure script
