Independent market intelligence
Research over noise · Risk before return
Crypto exchange research

Proof of Reserves: what an exchange proves—and what it does not

A wallet balance is evidence. It is not the whole balance sheet. This guide separates what a reserve snapshot can verify from the questions it leaves open.

5 min readReviewed 24 September 2026
01 / The two sides of the claim

The two sides of the claim

Proof of Reserves (PoR) usually starts with a dated snapshot: which customer assets an exchange says it holds, and what it owes customers in the assets covered by the report. Compare like with like—BTC reserves with BTC customer balances, not a blended dollar headline.

Reported assets÷Included client claims=Reported coverage
02 / What a Merkle proof verifies

What a Merkle proof verifies

A Merkle tree lets a customer check that their balance was included in a published set without exposing every other account. Inclusion is useful, but your proof alone cannot show that every customer was included or that off-chain obligations were counted. Read the stated scope and the independent reviewer’s work.

03 / Read a coverage ratio

Read a coverage ratio

The simple ratio is eligible assets ÷ included customer liabilities. A reported 120% means 120 units of assets for 100 units of included claims at that snapshot. It does not establish that all assets are free of liens, that no debts sit outside the report, or that the same position exists tomorrow.

A hypothetical coverage test

Change only the pledged amount. The figures below illustrate the arithmetic; they are not data about any exchange.

Reported assets: 120Included client claims: 100

How to read this comparison

The first bar divides all reported assets by included claims. The second subtracts the hypothetical pledged amount first. If pledged assets are unknown, the second figure cannot be measured from a PoR report alone.

Example only: 120 asset units and 100 client claim units. A pledge is a hypothetical constraint; whether any real assets are pledged requires separate evidence.
04 / The missing questions

The missing questions

A snapshot can miss changes between dates. It may not identify borrowed coins, pledged assets, excluded products, lost keys, or all corporate liabilities. Kraken describes several of these limits in its own methodology. PCAOB warns that PoR reports are not financial statement audits; the precise procedures and assurance vary.

05 / An eight-check workflow

An eight-check workflow

  1. 01Find the exact snapshot date and publication date.
  2. 02List included coins, networks, products and legal entities.
  3. 03Compare reserves with customer liabilities for each asset.
  4. 04Verify your own balance in the Merkle tree, if offered.
  5. 05Check how wallet control was established and whether assets are encumbered.
  6. 06Read the reviewer’s name, scope and actual conclusion.
  7. 07Look for full financial statements and other material obligations.
  8. 08Repeat the check after new reports; one snapshot is not ongoing proof.
06 / Sources and method

Primary sources

Research note: methods and report scope differ across exchanges. This page does not rate any platform or verify its current solvency.