Proof of reserves can support a scoped claim about assets held at a stated time, sometimes compared with included customer balances. Solvency requires a broader view of asset values and all obligations; liquidity additionally asks whether payments can be made when due. A reserve ratio above 100% does not, by itself, establish either. Read the report's entity, asset coverage, liability coverage, restrictions and timestamp before interpreting its headline percentage.
Start with the claim the report actually tests
“Proof of reserves” is not one universal procedure. A published wallet list, a customer-balance inclusion proof and an accountant's report answer different questions. Read the underlying document before combining them into a conclusion about the business.
A useful first sentence is: “This report compares these assets with these obligations for this entity at this time.” If the document does not supply one of those fields, record the gap. A recognizable exchange brand can cover several legal entities, products and custodians; evidence for one perimeter needs an explanation before it can support another.
Kraken, for example, describes an accountant aggregating in-scope client balances into a Merkle tree and comparing them with on-chain balances for which Kraken produces signatures. That includes customer-balance evidence, rather than merely displaying wallets. Its documentation also says verification reflects the snapshot's in-scope balances, excluding subsequent activity and out-of-scope assets. This is one provider's methodology, not a definition binding every reserve report. Kraken's proof-of-reserves methodology.
Separate reserve coverage, net assets and payment capacity
These checks use different denominators and time horizons. A ratio can be calculated correctly while answering a narrower question than the reader assumes.
| Check | Question answered | Evidence still needed |
|---|---|---|
| Scoped reserve coverage | Do identified reserves cover the included balances at the snapshot? | Exact assets, included claims and matching timestamp |
| Whole-entity financial position | What remains after all modeled liabilities are deducted from asset values? | Complete obligations, valuation and entity perimeter |
| Near-term liquidity | What can actually be delivered against payments due now? | Restrictions, conversion time and payment schedule |
| Customer access | Can this customer obtain the asset through the documented route? | Contractual rights and operational availability |
The Federal Reserve's banking explanation distinguishes liquidity available for near-term obligations from capital, measured as assets less liabilities. That economic distinction is useful here; bank capital rules are not being applied to a crypto venue. This article uses a simplified balance-sheet view, not a legal insolvency test for any jurisdiction. Federal Reserve explanation of liquidity and capital.
Reconcile a hypothetical 110% reserve snapshot
Consider a fictional exchange, Harbor, at 12:00 UTC. Every figure below is in millions of hypothetical dollars. These are invented values, not estimates for a real business.
For this construction, customer balances are liabilities of the same entity that owns the listed assets. There are no separate trust assets, subsidiaries, guarantees, derivatives or unlisted obligations. Actual custody arrangements may require different accounting and legal analysis. Assume the asset values are reliable, and unpledged wallet assets can be converted immediately without fees or price changes.
| Harbor item | Asset value | Liability value | Timing or restriction |
|---|---|---|---|
| Wallet assets | 110 | — | 30 pledged; 80 immediately usable |
| Bank cash | 8 | — | Immediately usable |
| Receivable | 12 | — | Due in 90 days; cannot be sold now |
| Customer balances | — | 100 | 90 requested for withdrawal now |
| Secured borrowing | — | 25 | Due in 30 days; secured by the pledged 30 |
| Expense payables | — | 10 | Due in seven days |
| Total | 130 | 135 | All amounts at the same snapshot |
Suppose a narrow reserve display compares wallet assets of 110 with customer balances of 100. Its displayed ratio is 110 ÷ 100 = 110%. The arithmetic is sound. Its scope omits borrowing and expense payables.
The complete modeled liabilities are 100 + 25 + 10 = 135. Total modeled assets are 110 + 8 + 12 = 130. Their difference is 130 − 135 = −5. Harbor has negative modeled equity despite the 110% headline reserve ratio. The extra 10 of wallet assets above customer balances is not automatically surplus capital once other creditors are included.
Now ask a separate payment question. The pledge cannot be released during this immediate withdrawal window. Available resources are 110 − 30 + 8 = 88. Against 90 of withdrawal requests, the modeled gap is 88 − 90 = −2. The receivable contributes to the assumed asset value but cannot fund today's requests.
Do not deduct the pledged 30 again when calculating equity. It remains an asset in this construction, and the secured debt of 25 is already a liability. Removing collateral from available liquidity is appropriate under the stated restriction; subtracting it again from total assets would answer a different question and misstate this ledger.
Two variations isolate the issues further. If the receivable is worth only 6 instead of 12, total assets fall to 124 and equity to −11, while the displayed wallet-to-customer ratio remains 110%. In a separate alternative balance sheet, a fully valued receivable of 22 would make equity +5, but immediate resources would remain 88. A positive net-asset calculation would still not fund the 90 requested now.
These examples deliberately remove market conversion costs. Adding token price changes, settlement delays or forced-sale discounts would require new inputs, not a claim that the original calculation already captured them.
Check what cryptographic inclusion does and does not establish
A customer can use a supported inclusion proof to check that a particular balance was committed into a particular dataset. That is useful evidence about the record checked. It does not let that customer inspect an unseen corporate loan, establish every other account's completeness, or determine contractual priority from the hash alone.
Likewise, demonstrating control of an address at one moment is a different task from establishing that its assets are free from other claims. Kraken explicitly lists limitations involving hidden encumbrances, funds borrowed for the review and subsequent key loss or theft. Those are acknowledged limits of its described procedure; they are not allegations that those events occurred. Kraken's stated proof-of-reserves limitations.
For assets that are themselves representations of other assets, investigate the underlying claim as well. The wrapped-token and bridge-risk guide traces dependencies that a visible token balance can leave unresolved. Counting units is only one part of understanding what those units can deliver.
Reconcile time as carefully as amounts
A snapshot remains tied to its observation time. A correct historical comparison cannot automatically describe the current balance sheet.
Suppose Harbor borrowed 25 immediately before the review. If that borrowing increased wallet assets by 25 and debt by 25, its net assets did not increase. Returning the loan later would reduce both by 25, again without creating equity. A wallet-only comparison can change sharply while that net-asset effect stays zero.
For a real report, save the snapshot timestamp, report date and date you read it. Then look for the period covered by any procedures addressing movements around the snapshot. The PCAOB Office of the Investor Advocate warns that reserve reports can omit borrowed-asset and liability questions and do not establish that assets remained available after issuance. Its advisory is staff guidance about report limitations, not a determination about a particular platform. PCAOB reserve-report advisory.
Do not interpret every on-chain movement as a customer deposit, withdrawal or profit. Even an observed transaction requires attribution. The SOPR methodology guide addresses a related boundary: a chain-derived measure depends on its defined inputs and cannot identify every economic event from movement alone.
Read the engagement before reading the badge
Identify who prepared the report, which standards or procedures it names, what conclusion it expresses and what it excludes. The word “audit” in marketing copy does not resolve those questions.
The SEC's investor bulletin explains that proof-of-reserves reports are not equivalent to financial-statement audits under SEC rules and PCAOB standards. A firm's PCAOB registration also does not mean every service it provides falls under PCAOB oversight. This is a distinction about the engagement, not a claim that every crypto venue has the same US reporting obligations. SEC bulletin on alternatives to financial-statement audits.
Where broader financial statements are available, match their entity and period to the reserve report and read the notes. Evidence with different boundaries can complement each other, but the boundaries need to be reconciled explicitly.
Keep a reserve-report review worksheet
Use “not disclosed” when evidence is unavailable. An unknown is neither proof of a shortfall nor permission to assume the missing amount is zero.
| Review field | Record this evidence | Failure case to catch |
|---|---|---|
| Entity and products | Named entity, covered services and exclusions | Applying one entity's report to the entire brand |
| Asset identity | Native asset or claim, quantity and valuation basis | Treating unlike assets as interchangeable dollars |
| Customer claims | Included balances and account-adjustment rules | Assuming your own inclusion proves every liability exists in the dataset |
| Other obligations | Borrowing, expenses and relevant commitments | Treating reserves above customer balances as equity |
| Restrictions | Pledges, release terms and other claims on assets | Counting controlled assets as immediately deliverable |
| Timing | Snapshot, procedures, report and review dates | Using an old balance to describe current availability |
| Engagement | Provider, standards, findings and exclusions | Reading a badge as a broader assurance opinion |
Keep entity-level reserves separate from an account allocation. A subaccount boundary review addresses which balances and authorities a process can affect; it does not establish its exchange's financial condition. Similarly, stablecoin redemption and liquidity examines whether a reserve asset can become the settlement asset needed within the required time.
Finish the worksheet with one dated sentence stating the claim the evidence supports, followed by the first material unresolved field. For Harbor, that sentence would preserve the 110% scoped calculation while also showing negative $5 million of modeled equity and a separate $2 million immediate funding gap.