Proof of Reserves Without Proof of Liabilities, Explained
Cryptographic wallet attestations can confirm what an exchange controls on-chain, but solvency requires measuring total obligations, unencumbered collateral, and hidden off-balance-sheet debt.
Key points
- Proof of reserves verifies on-chain asset custody at a specific point in time but completely omits off-chain liabilities, bank loans, and unrecorded debt.
- Merkle tree proofs enable users to verify individual account inclusion, but platforms can still manipulate results by omitting large accounts from the source dataset.
- Agreed-upon procedures (AUP) engagements only test narrow client-defined metrics and do not constitute full, independent corporate balance sheet audits.
- Regulators including ESMA under MiCA and the US SEC warn that isolated reserve attestations fail to provide comprehensive solvency assurance.
A custodial crypto exchange that publishes cryptographic evidence of its wallet holdings proves only what it holds, not what it owes. Proving that an entity controls private keys associated with digital assets is fundamentally half of a solvency equation. Without a verifiable, comprehensive accounting of customer obligations and external debts, an entity can display massive asset reserves while remaining completely insolvent.
The Solvency Equation
Solvency is simple arithmetic: total assets must exceed total liabilities. In traditional finance, evaluating a firm's balance sheet requires evaluating both sides of the ledger simultaneously.
In the digital asset industry, proof of reserves emerged as a mechanism to allow centralized platforms to demonstrate control over specific on-chain balances. A platform signs a message using its private keys or moves funds between designated addresses to show ownership of native assets such as $BTC or $ETH.
However, proof of liabilities represents the other half of the balance sheet: the cumulative sum of all claims that users and third-party creditors hold against the platform. Showing assets in isolation confirms custody of funds at a specific point in time. It does not confirm that those assets are free from competing legal claims, pledged as collateral elsewhere, or sufficient to satisfy total depositor balances.
Cryptographic Attestations and Merkle Trees
To demonstrate customer liabilities without exposing sensitive user account balances, centralized custodians frequently deploy Merkle trees. A Merkle tree is an efficient, cryptographically verifiable data structure where individual balances are hashed into leaf nodes and iteratively combined into a single top-level Merkle root hash.
Under this process, an exchange takes an internal snapshot of its database containing every user's asset balance. Each user balance forms a leaf node alongside an anonymized user identifier. Pairs of leaf nodes are hashed together repeatedly up the tree until one root hash is generated. The platform publishes this root hash. A depositor can take their individual account balance and verification path to confirm that their specific account was included in the total liability calculation.
More advanced implementations use zero-knowledge cryptography, such as zero-knowledge succinct non-interactive arguments of knowledge (zk-SNARKs). As explored in Proof of Reserves: What It Shows and What It Hides, zero-knowledge rollups allow platforms to demonstrate that each user balance is non-negative and that the aggregate balance correctly sums individual accounts without revealing individual account sizes to the general public.
Yet, even cryptographic liability trees contain a critical vulnerability: the platform controls the ingestion of data into the tree. If an operator selectively omits large accounts or inserts negative balances to artificially reduce the total aggregate sum, the Merkle root calculation will be mathematically valid but economically fraudulent.
The Reality of Off-Balance-Sheet Debt
A purely on-chain snapshot or Merkle aggregation cannot capture off-balance-sheet commitments. Digital asset custodians operate within a global financial network involving fiat banking rails, institutional lending desks, and contractual agreements that leave no footprint on public blockchains.
Consider an exchange that publishes an on-chain attestation showing 10,000 $BTC held in cold storage. On the surface, the reserve appears fully funded against customer deposits of 10,000 BTC. However, the attestation cannot capture whether the exchange:
- Borrowed those 10,000 tokens from an institutional market maker for 48 hours under a master loan agreement simply to take the attestation snapshot.
- Pledged those same tokens as encumbered collateral to an over-the-counter (OTC) lender under a rehypothecation agreement.
- Incurred non-crypto liabilities, such as outstanding lines of credit from traditional banks, corporate bond obligations, or pending legal judgements.
Because blockchain nodes only process state transitions defined by protocol consensus rules, an on-chain ledger cannot register a legal lien placed on an asset via a commercial contract signed in a foreign jurisdiction. An asset that appears fully liquid and unencumbered on a blockchain explorer may be legally encumbered by a senior secured creditor.
A Worked Example: The Solvency Illusion
To understand how an attestation can mask insolvency, consider a simplified exchange balance sheet under two reporting models: a stand-alone proof of reserves attestation versus a full balance sheet audit. Assume all token values are evaluated at parity for simplicity.
Suppose Exchange A holds customer deposits totaling 50,000 BTC. Unknown to its retail users, the platform suffered an operational loss of 20,000 BTC due to trading losses or unrecoverable loans. To prepare for an upcoming public reserve snapshot, the firm executes a short-term term loan with an institutional lender, borrowing 20,000 BTC for five days at an agreed interest rate, delivered directly to its cold storage addresses.
When the snapshot occurs:
- The on-chain Proof of Reserves attestation records 50,000 BTC under the platform's control.
- The self-generated Merkle tree of liabilities lists 50,000 BTC of retail depositor balances.
- The resulting public reserve ratio is published as exactly 100 percent (50,000 BTC divided by 50,000 BTC).
Under a comprehensive balance sheet accounting, the true financial position is revealed:
- Total Assets: 50,000 BTC
- Customer Liabilities: 50,000 BTC
- Senior Creditor Loan: 20,000 BTC
- Total Liabilities: 70,000 BTC
- Net Equity: -20,000 BTC
The platform has a reserve deficit of 20,000 BTC and an actual reserve coverage ratio of 71.4 percent. The moment the short-term institutional loan matures, the platform must return the borrowed assets. If depositors attempt to withdraw their funds simultaneously, the platform faces a liquidity run and suspension of withdrawals.
Attestations vs. Independent Audits
Market participants often confuse an agreed-upon procedures (AUP) engagement with a comprehensive statutory financial audit. They are fundamentally different professional exercises governed by distinct international accounting standards.
An agreed-upon procedures engagement is not an audit. Under professional standards established by bodies like the American Institute of Certified Public Accountants (AICPA) or the International Auditing and Assurance Standards Board (IAASB), an accounting firm performing an AUP does not issue an opinion or provide audit assurance. Instead, the practitioner merely executes narrow, pre-defined steps specified by the client. For instance, the exchange may instruct the accountant to verify that the private keys for five specified addresses signed a specific text string at 12:00 UTC on a single date, and that the internal database showed a matching total at that exact instant. The accountant publishes factual findings without verifying whether other hidden liabilities exist, whether internal controls are effective, or whether the company is solvent.
A full financial audit requires a certified public accountant or statutory auditor to examine the entity in accordance with Generally Accepted Auditing Standards (GAAS) or International Standards on Auditing (ISA). An auditor evaluates internal operational controls, directly contacts banking partners and institutional creditors to confirm balances independently, reviews pending litigation, and evaluates subsequent events to provide reasonable assurance that the financial statements are free of material misstatement.
Attestation reports that omit third-party liabilities or rely strictly on management representations fail to provide the assurances associated with conventional corporate balance sheet audits.
Regulatory Frameworks and Disclosure Requirements
Financial regulators in primary jurisdictions have increasingly addressed the structural limitations of isolated cryptographic attestations, establishing formal requirements that separate regulated custody from unmonitored self-reporting.
In the European Union, the Markets in Crypto-Assets (MiCA) regulation enforces strict operational, custody, and capital requirements on Crypto-Asset Service Providers (CASPs). Under MiCA, regulated entities holding client assets must segregate depositor assets from proprietary trading books, maintain minimum regulatory capital reserves, and face supervision by national competent authorities in coordination with the European Securities and Markets Authority (ESMA). MiCA prohibits the rehypothecation of customer crypto-assets for the custodian's own account.
In the United States, the Securities and Exchange Commission (SEC) staff has issued guidance highlighting the risks of client-commissioned PoR reports. The SEC's Office of the Chief Accountant cautioned investors that non-audit attestations lack standardized criteria and may omit critical liability data. Concurrently, state-level regulators such as the New York State Department of Financial Services (NYDFS) require regulated virtual currency entities under the BitLicense regime to maintain full asset segregation, maintain robust accounting controls, and submit to regular, exhaustive state financial examinations.
In the United Kingdom, the Financial Conduct Authority (FCA) enforces strict anti-money laundering registration and consumer protection regimes that scrutinize operational resilience and financial soundness, warning that marketing claims of safety based purely on balance-sheet snapshots can mislead consumers.
Common Misconceptions
- A 100% Proof of Reserves ratio means an exchange cannot fail. An attestation showing a 100 percent or higher reserve ratio indicates only that assets matched reported liabilities at the precise second the snapshot was taken. It does not account for loans, debts to third-party trading firms, operational overhead, legal claims, or intraday asset movements.
- Merkle tree verification prevents an exchange from manipulating liability data. While Merkle trees prevent tampering after the root hash is published, they do not guarantee the completeness of the underlying input data. A platform can conceal accounts, omit institutional creditors, or present an incomplete database to the verification program.
- Cryptographic attestations are equivalent to traditional corporate audits. An attestation or agreed-upon procedures report does not evaluate the broader corporate structure, revenue, off-chain obligations, or overall solvency. Certified financial audits require comprehensive examinations of debts, banking contracts, and external claims that software tools cannot observe on a blockchain.
How This Connects to the Market
Cryptographic accounting represents an important technical leap toward transparent financial recordkeeping, but it must be viewed as an adjunct to, rather than a replacement for, standard balance-sheet audits. Verifying that a platform holds digital assets proves technical custody, yet true financial health hinges on the legal status of those funds.
Market participants evaluating custodial risk should distinguish between point-in-time cryptographic snapshots and ongoing regulatory compliance. The structural risks of custodial platforms—such as unannounced lending, commingled accounts, and rehypothecation—remain commercial and contractual risks, not algorithmic ones. Until cryptographic protocols can ingest and verify all global legal obligations in real time, solvency will remain contingent on enforceable accounting standards, statutory audits, and rigorous regulatory oversight.
Questions this story raises
- What is the primary limitation of a Proof of Reserves attestation?
- Proof of reserves only verifies that a platform controls specific cryptographic addresses with a given balance. It cannot reveal whether those assets are encumbered by liens, borrowed temporarily for the snapshot, or exceeded by off-balance-sheet corporate debts.
- How does a Merkle tree verify customer liabilities?
- A Merkle tree aggregates individual user account balances into a single cryptographic root hash. Users can use their individual account keys and a cryptographic branch to verify their balance was included in the total sum without seeing other users' balances.
- Why is an agreed-upon procedures report not considered a financial audit?
- In an agreed-upon procedures report, the accountant only executes specific instructions provided by the platform (such as checking address signatures) without issuing an audit opinion, validating internal controls, or investigating undisclosed debts.
- Can an exchange borrow assets temporarily to pass an on-chain reserve check?
- Yes. A platform can borrow funds via short-term loans or credit facilities immediately before a snapshot, deposit them into visible reserve wallets, and return the assets after the snapshot without the transaction violating protocol rules.
References
- [1] Staff Statement on Proof of Reserves Reports — U.S. Securities and Exchange Commission
- [2] International Standard on Related Services 4400 (Revised): Agreed-Upon Procedures Engagements — International Auditing and Assurance Standards Board
- [3] Guidance on Custody of Customer Virtual Assets — New York State Department of Financial Services
- [4] Markets in Crypto-Assets Regulation (MiCA) — European Securities and Markets Authority
Evergreen explainer written by Basis Desk's system and checked by an independent model pass for factual errors and advice language. Figures, fees and rules change — the references above are where to verify current specifics. Market figures marked "at the time of writing" come from live exchange data. Report an error: corrections@basisdesk.news · corrections policy.
The Daily Brief, in your inbox at 07:00 ET
Five stories, the numbers that moved, what to watch. Three minutes. No hype, no advice, unsubscribe in one click.
Get the big crypto stories first
A few alerts a day at most: major breaking news and the morning brief. Switch off anytime.
Not financial advice. Basis Desk publishes information, not recommendations. Crypto assets are volatile and you can lose what you invest.