A proof-of-reserves report can provide useful evidence about an exchange’s assets, but it is not automatically proof that customer funds are fully protected. This guide explains how to evaluate an exchange solvency disclosure, compare reserves with liabilities, inspect custody controls, and document risks before depositing a significant balance.
Overview
Proof of reserves is a process intended to show that a crypto exchange or custodian controls certain digital assets at a stated point in time. The evidence may include wallet addresses, balances recorded on a blockchain, and a report from an auditor or independent attestation provider. The format and depth of these disclosures vary widely.
The central limitation is simple: proof of reserves is not the same as proof of solvency. Reserves address what an entity appears to hold. Solvency also requires understanding what it owes, whether customer assets are segregated, and whether other claims or obligations could affect withdrawals. A report that shows Bitcoin in controlled wallets may not reveal fiat liabilities, unsecured borrowing, contingent obligations, or assets held elsewhere.
Use a reserves report as one part of a broader counterparty-risk review. A useful assessment should answer four questions:
- What assets were measured, and on what date?
- Who verified the balances and what procedures were performed?
- Were customer liabilities included and reconciled to the reserves?
- What legal, operational, and custody risks remain after the disclosure?
For broader custody decisions, compare exchange storage with self-custody and other wallet arrangements using a documented security process. The crypto wallet selection and migration checklist can help with that comparison.
Checklist by scenario
When reviewing a new exchange
- Find the official disclosure. Start with the exchange’s official website, investor materials, regulatory filings where applicable, or clearly identified provider reports. Treat screenshots, social-media posts, and unauthenticated documents as leads rather than evidence.
- Record the reporting date. A reserves report is a snapshot. Save the publication date, measurement date, covered entities, and supported assets. A report that is old or issued only after a market event may provide limited information about current conditions.
- Identify the verifier. Determine whether the document is an audit, an attestation, a review, or a self-published disclosure. These terms can involve different levels of testing. Read the scope and procedures instead of relying only on a provider’s logo or the word “verified.”
- Check liabilities coverage. Look for a customer-balance or proof-of-liabilities section. Confirm whether the report covers all customers, only participating customers, selected assets, or a particular legal entity.
- Review custody details. Look for information about segregated wallets, omnibus accounts, third-party custodians, lending, rehypothecation, withdrawal permissions, and internal transfers. Missing information is itself a risk factor to record.
When an exchange publishes a new report
Compare the new report with the previous one rather than reading it in isolation. Note changes in reserve composition, wallet addresses, covered subsidiaries, excluded assets, and liabilities methodology. A larger reserve balance does not automatically mean lower risk if customer obligations or custody arrangements also changed.
If wallet addresses are disclosed, use a reputable blockchain explorer to inspect balances and transaction history. Confirm that the network and token contract are correct, and avoid treating a visible balance as definitive proof of beneficial ownership. An address may be controlled by a custodian, shared across customers, or temporarily funded for measurement. The blockchain explorer guide provides a practical method for checking on-chain evidence.
When deciding how much to keep on an exchange
Separate trading liquidity from long-term holdings. Keep only the amount needed for a defined purpose when the exchange’s custody, withdrawal, legal, or financial disclosures remain unclear. Consider withdrawal limits, processing delays, supported networks, account freezes, and recovery procedures before transferring funds. A reserves report cannot eliminate platform, cyber, market, or insolvency risk.
What to double-check
| Area | More useful disclosure | Warning sign |
|---|---|---|
| Attestation or audit | Names the provider, procedures, limitations, and responsible legal entity. | Uses broad verification language without explaining the work performed. |
| Scope | States the measurement date, entities, assets, networks, and exclusions. | Shows a single total with no date or coverage boundaries. |
| Liabilities | Explains how customer balances were identified, reconciled, and included. | Reports assets only or covers liabilities selectively. |
| Wallet transparency | Provides addresses or a credible method for independently checking balances. | Displays balances that cannot be linked to a controlled wallet or custodian. |
| Reserve composition | Breaks out assets and identifies restrictions or illiquid holdings. | Counts affiliated, thinly traded, borrowed, or unclear assets without explanation. |
| Asset segregation | Explains whether customer assets are separated from corporate funds and third-party claims. | Leaves ownership and commingling arrangements unclear. |
| Withdrawal controls | Describes approval controls, limits, outage procedures, and incident communication. | Provides no practical information about how withdrawals are processed. |
| Bankruptcy protection | Publishes clear custody terms and the applicable legal entity and jurisdiction. | Assumes a reserves statement guarantees recovery if the platform fails. |
Also distinguish between proof of reserves and proof of liabilities. Reserves can be checked on-chain, while liabilities generally depend on internal records and the method used to protect customer privacy. A strong disclosure should explain how the two sides were compared, including whether liabilities exceeded reserves for any asset.
Common mistakes
- Treating a snapshot as a guarantee. Assets can move after the measurement date, and a snapshot does not describe every day of operations.
- Confusing an attestation with a full financial audit. Read the report’s scope, limitations, and procedures before assigning it more weight than it deserves.
- Ignoring liabilities. A platform can hold substantial assets and still face serious obligations, borrowing arrangements, or legal claims.
- Assuming disclosed wallets prove ownership. On-chain balances do not independently establish who controls an address or whether assets are encumbered.
- Accepting native tokens at face value. An exchange’s own token may be liquid under normal conditions but difficult to sell during stress. Record its share of total reserves and the assumptions behind its valuation.
- Overlooking operational security. Multisignature controls, withdrawal approvals, access management, incident response, and insurance terms can matter as much as reported balances.
- Relying on a single source. Compare the exchange’s disclosure with its terms of service, custody policy, regulatory information, withdrawal experience, and credible security reporting.
Do not allow a clean-looking report to replace basic risk management. Diversifying custody, testing a small withdrawal, enabling strong account security, and keeping transaction records can reduce avoidable exposure. Never share seed phrases or private keys with an exchange, auditor, support agent, or person claiming to verify reserves.
When to revisit
Recheck an exchange’s solvency and custody disclosures before moving a large balance, opening a new account, or relying on the platform for a major trading or payment workflow. Review the assessment whenever the exchange publishes a new report, changes its legal entity or terms, adds a lending or yield product, experiences withdrawal disruption, discloses a security incident, or faces material regulatory or insolvency news.
A quarterly review is a practical baseline, even when no obvious event occurs. Create a simple record containing the report URL, measurement date, covered entities, reserve-wallet addresses, asset breakdown, liabilities methodology, custody terms, withdrawal test results, and unresolved questions. Mark each item as confirmed, unclear, or contradicted by other information.
Before depositing, use the record to set a personal exposure limit and define an exit plan. If you cannot explain what the report covers, what it excludes, and how customer claims would be treated during a failure, treat that uncertainty as a reason to reduce exposure or seek more information. Proof of reserves can improve transparency, but careful documentation and custody discipline remain the more durable protection.
