cryptobank
Crypto Bank is an independent editorial publication. It is not a bank, is not a deposit-taking or custodial institution, holds no banking, trust, money-transmitter or e-money licence, and offers no FDIC or FSCS protection. Nothing here is financial, legal or investment advice.
BTC $63,224-0.77% ETH $1,773-0.88% USDT $1.00+0.10% USDC $1.00+0.01% SOL $73.99+2.41% XRP $0.98+2.53% BNB $584-0.40% ADA $0.15+0.59%
Reading a Proof-of-Reserves Page: A Field Checklist With Worked Examples

GUIDE

Reading a Proof-of-Reserves Page: A Field Checklist With Worked Examples

Crypto Bank Editorial Team · November 18, 2026

Proof of reserves was the industry’s answer to a specific failure: customers could not tell a platform that held their assets from one that had lent them out, because the evidence lived only inside the company. Publishing it is better than not. But a reserves page is easy to over-read, and the same headline (“1:1 backed”, “100%+ reserves”) can sit on top of very different work. This is a field checklist: seven questions to ask of any page, and how three real pages answer them. For the conceptual limits, read our companion guide, proof of reserves and what it cannot prove.

The seven checks

  1. Who did the work? A named firm that signs the report and can be held to it, or the platform itself? An unnamed “independent auditor” is closer to the second than the first.
  2. What kind of engagement? An attestation on agreed procedures, or a financial-statement audit? The words are used loosely; the assurance is not the same. See attestation vs audit.
  3. Are liabilities in scope? Solvency is assets against obligations. A page that only proves control of addresses shows half a balance sheet. The usual liability method is a Merkle tree of customer balances that lets each customer confirm they were counted.
  4. What stops the total being understated? A Merkle sum can be gamed with negative or fictitious balances unless the scheme constrains the arithmetic at every node. Look for an explicit statement of how that is prevented.
  5. When, and how often? A snapshot on a known date can be met with borrowed assets that leave the next day. Frequent, unannounced snapshots make that expensive.
  6. Which assets? All client assets, or a selection? Check that the asset list is the same everywhere on the page.
  7. What about encumbrances? Signing for an address proves access to a key, not that the coins are free of pledges, loans or repurchase agreements. Off-chain obligations are invisible on-chain, and they are where leverage usually hides.

Three worked examples (checked 2026-11-18)

Kraken

The page says the review is performed by “an independent third-party auditor” but does not name the firm. The latest snapshot shown was 30 September 2026. The method checks that holdings are not less than customer balances recorded in a Merkle tree, so the customer-liability side is addressed; other liabilities are not discussed. One detail fails check 6: the asset table and the FAQ list different sets of covered assets. Kraken separately states that accounts are not covered by insurance against losses. See the Kraken profile.

Binance

The page describes a self-run scheme: a Merkle tree of user balances, plus zk-SNARK proofs intended to show that every leaf contributes to the claimed total and that net balances are not negative. That addresses check 4 directly. No third-party firm is named (check 1), and the snapshot date was not visible in our capture of the page (check 5). Binance says it holds all user assets 1:1 and has a SAFU emergency fund; the fund is not insurance. See the Binance profile.

Paxos (USDP reserves)

A different kind of page, because Paxos issues tokens and attests to the reserves behind them. The USDP transparency page names the firm: KPMG LLP for reports posted on or after 28 February 2025, WithumSmith+Brown, PC before that, under AICPA attestation standards, with monthly reports listed through September 2026. Checks 1, 2 and 5 are answered clearly. Paxos separately states its reserves are held in bankruptcy-remote accounts; that is its own legal characterisation. See the Paxos profile.

What a clean page still does not prove

Even a page that passes every check is a statement about a moment, about the assets and liabilities in scope, under the engagement terms of the firm that did it. It does not tell you how client assets would be treated if the platform failed; that depends on segregation and the governing law. A platform can publish a clean proof and its customers can still rank as unsecured creditors later. The two questions are separate, and our guide on client assets in insolvency covers the second.

The Custody Question, applied

  • Who holds the keys: a reserves page confirms that someone controls certain addresses at a moment, not whose property the coins are.
  • Who insures it: nothing on a reserves page is insurance; read the insurance disclosure separately.
  • What happens on default: answered by the custody terms and the law, not by the proof.

Sources

Editorial explainer, not financial or legal advice. Crypto Bank is not a bank and does not hold client assets.