Proof of reserves: what the report covers and what it leaves open

Start with the claim and its date

A proof of reserves (PoR) is a label used for different engagements and technical disclosures. Begin with the exact report, publisher, reporting entity, product, asset set, liability set, method and snapshot time. A report is evidence about the work and scope it describes; the label alone does not show that all obligations were counted or that a platform is financially sound.

The PCAOB Office of the Investor Advocate staff advisory dated 8 March 2023 warns that PoR reports are inherently limited and are not audits under PCAOB auditing standards. The advisory describes point-in-time asset verification whose procedures may not address liabilities, holders’ rights, borrowed assets, later use of the assets, internal controls or governance. The document itself says it represents staff views, not a PCAOB rule or policy. SEC Chief Accountant Paul Munter’s 27 July 2023 statement separately warns that non-audit crypto work is not equivalent to a financial-statement audit; it is an official-capacity staff statement, not a Commission rule.

Evidence: PCAOB staff PoR advisory (scope-limited) · SEC staff statement on non-audit work

The advisory says it reflects Investor Advocate staff views, not a PCAOB rule, policy or Board statement. Used for its warning on point-in-time scope, liabilities, borrowed assets, non-uniform engagements, controls and future protection; not universal legal advice.

The statement says it is provided in the author's official capacity, does not necessarily reflect Commission views, and has no legal force or effect. Used for distinguishing non-audit crypto work from a financial-statement audit; it is not a rule or universal service description.

Read the scope before reading a ratio

Use this paper checklist for a dated report. If a field is missing, mark it unknown; do not silently fill it from a brand name, reserve address or token ticker.

Evidence: PCAOB staff PoR advisory (scope-limited) · Binance.com’s own PoR method page

The advisory says it reflects Investor Advocate staff views, not a PCAOB rule, policy or Board statement. Used for its warning on point-in-time scope, liabilities, borrowed assets, non-uniform engagements, controls and future protection; not universal legal advice.

This is the platform's own description of Merkle/zk-SNARK inclusion verification. No particular report, date, asset values, customer account, legal entity, regional service or independently audited result was checked. Do not treat its page copy as independent assurance.

Assets and customer liabilities are different sides of the question

A reserve address or asset list shows selected on-chain holdings at a time if the reported address attribution and measurement are correct. A liability computation describes obligations within its chosen population and method. To compare them, check that asset and liability units match and that the same entity, services and snapshot are in scope. A reserve proof alone may not identify debts to lenders, affiliates, employees or other parties; the PCAOB staff advisory specifically cautions that some procedures may not address liabilities or whether assets were borrowed.

Do not turn a ratio into a guarantee. A reserve asset could be encumbered, borrowed, controlled through a third party, or later transferred; whether any of these apply must be established from the specific report and other evidence. A ratio also does not settle the customer’s legal rights, segregation, insolvency priority, internal controls or the platform’s total financial condition.

Evidence: PCAOB staff PoR advisory (scope-limited) · SEC staff statement on non-audit work

The advisory says it reflects Investor Advocate staff views, not a PCAOB rule, policy or Board statement. Used for its warning on point-in-time scope, liabilities, borrowed assets, non-uniform engagements, controls and future protection; not universal legal advice.

The statement says it is provided in the author's official capacity, does not necessarily reflect Commission views, and has no legal force or effect. Used for distinguishing non-audit crypto work from a financial-statement audit; it is not a rule or universal service description.

How to treat a platform’s own verification page

Binance.com’s Proof of Reserves page, consulted on 26 October 2026, describes its method using a Merkle tree and zk-SNARKs and explains that an account record can be checked for inclusion in a specified liabilities computation and verification date. That is Binance’s own description of its process. I did not log in, inspect a customer account, open a particular dated report, check a wallet, reproduce a proof or verify the platform’s claims.

This platform page is not an independent assessment of every Binance legal entity, service, region, customer claim or later date. Do not carry a report’s figures forward as current balances. If a future reader considers a particular report, use the exact report date and entity, read its own scope and methodology, and compare it with current terms for the specific service and location. A page describing a proof flow does not make that flow a full financial-statement audit.

Evidence: Binance.com’s own PoR method page · PCAOB staff PoR advisory (scope-limited)

This is the platform's own description of Merkle/zk-SNARK inclusion verification. No particular report, date, asset values, customer account, legal entity, regional service or independently audited result was checked. Do not treat its page copy as independent assurance.

The advisory says it reflects Investor Advocate staff views, not a PCAOB rule, policy or Board statement. Used for its warning on point-in-time scope, liabilities, borrowed assets, non-uniform engagements, controls and future protection; not universal legal advice.

Solved fictional example: 105.3% is not a solvency verdict

Hypothetical paper case only; no real company, report, address or account was consulted. A dated document says that 100 X of an asset is in the reported reserve set and that 95 X of customer balances are in its stated liability set. On that narrow same-asset comparison, 100 ÷ 95 = 1.0526, or about 105.3%. This calculation assumes the reported amounts and scope are correct; it does not validate them.

Now stress-test the scope, without pretending this is an adjustment to an actual report: suppose a separate 20 X obligation exists but is outside the stated customer-liability set. The hypothetical obligation total would be 95 + 20 = 115 X, so 100 ÷ 115 ≈ 0.8696, or 87.0%. The example demonstrates why the denominator matters; the extra obligation is invented, not evidence that any platform has it. Neither percentage establishes ownership free of liens, full liabilities, withdrawal capacity, a legal claim, or future solvency.

Evidence: PCAOB staff PoR advisory (scope-limited)

The advisory says it reflects Investor Advocate staff views, not a PCAOB rule, policy or Board statement. Used for its warning on point-in-time scope, liabilities, borrowed assets, non-uniform engagements, controls and future protection; not universal legal advice.

Write a bounded conclusion, not a trust verdict

A careful note might say: “This document reports evidence about the listed assets and the defined liability data at the stated snapshot. I checked the named entity, asset units, liability population, date and described procedure. The document does not establish a complete company balance sheet, all creditor obligations, absence of borrowing or encumbrances, effective controls, a right to withdraw, or the position after the snapshot.” Replace each item only when the specific report supports it.

Comprehension check: a fictional inclusion proof shows a customer leaf was included in a Merkle calculation tied to a dated root. Does that prove the whole platform is solvent and can return the balance tomorrow? No. It supports only the inclusion claim for that data set and time, subject to the stated proof system and report scope. If the report omits the liability population or procedures, stop and record that limitation as unknown.

Evidence: PCAOB staff PoR advisory (scope-limited) · Binance.com’s own PoR method page · SEC staff statement on non-audit work

The advisory says it reflects Investor Advocate staff views, not a PCAOB rule, policy or Board statement. Used for its warning on point-in-time scope, liabilities, borrowed assets, non-uniform engagements, controls and future protection; not universal legal advice.

This is the platform's own description of Merkle/zk-SNARK inclusion verification. No particular report, date, asset values, customer account, legal entity, regional service or independently audited result was checked. Do not treat its page copy as independent assurance.

The statement says it is provided in the author's official capacity, does not necessarily reflect Commission views, and has no legal force or effect. Used for distinguishing non-audit crypto work from a financial-statement audit; it is not a rule or universal service description.