Proof of Reserves

What is Proof of Reserves, and how is it different from an exchange simply saying "our funds are safe"?

Proof of Reserves (PoR) is a cryptographic method that lets an exchange prove its held assets are sufficient to cover all customer liabilities, without exposing any individual user's account privacy. The core tool is the Merkle Tree — a data structure that aggregates every user's balance, layer by layer through a Hash Function, into a single "root hash." If any single user's balance changes, that root hash changes along with it, meaning the exchange cannot quietly adjust any single account entry without it being detectable. Each user can obtain their own "verification path," independently confirming that their balance really is included in that root hash — without ever needing to see anyone else's account information.

The fundamental difference from an exchange unilaterally declaring "our funds are safe" is verifiability: no matter how formal a verbal statement or internal document sounds, a user has no way to independently check whether it's true — they can only choose to believe it or not. Proof of Reserves instead turns "believing" into a mathematical problem you can verify yourself — even without fully understanding the cryptographic details, a user can use the tool the exchange provides to personally confirm whether their own account balance was honestly included.

Why has Proof of Reserves been widely adopted, and what problem is this mechanism meant to solve?

The concept of Proof of Reserves existed even before FTX collapsed in November 2022, but it only became genuinely widely valued and implemented across the industry after the FTX incident — when FTX collapsed, it was discovered that a roughly $8 billion gap existed between customer-deposited assets and what the exchange actually held. Before that, the overwhelming majority of users had no idea this gap existed at all, because an exchange's asset and liability position was entirely a black box, and users could only judge whether their funds were safe based on information the exchange unilaterally chose to provide. That incident made the entire industry realize that relying solely on "trusting the brand" or "trusting the exchange's own statements" is extremely fragile under conditions of complete information asymmetry.

The core problem Proof of Reserves is meant to solve is exactly this: converting that information-asymmetric black box into a transparent system users can verify for themselves. This is also why mainstream exchanges progressively adopted Proof of Reserves as a standard trust-building practice after FTX — not because regulators required it (most jurisdictions didn't mandate it at the time), but because in an industry where trust had been badly damaged, only exchanges able to offer verifiable evidence could win back user confidence. That's what turned Proof of Reserves from a technically feasible option into a de facto industry standard.

How does Proof of Reserves actually work, and how does the Merkle Tree protect privacy?

The full process typically involves collaboration between an exchange and an independent third-party auditor: the auditor takes a snapshot of every customer's balance at an agreed point in time, runs each balance (paired with the user's anonymized identifier) through a Hash Function, pairs and aggregates them layer by layer, and finally consolidates them into a single root hash that gets published publicly. At the same time, the auditor independently verifies the total assets the exchange actually holds — by examining the exchange's on-chain wallet addresses or requiring the exchange to provide signed messages — confirming that total equals or exceeds the sum of all customer balances at the moment of the snapshot.

The key design that protects privacy in a Merkle tree is that each user only receives their own small "verification path" (a series of adjacent Node hashes). Using that path, a user can independently compute the root hash and compare whether the result matches the root hash the exchange published — if it matches, it means their balance was genuinely and honestly included. But throughout this entire process, the user never sees anyone else's account balance or identity information at all, because the other hash values along the verification path are the results of other users' balances having already been hashed — themselves irreversible values that can't be reverse-engineered back into the original balance figures. Some exchanges (such as Binance) have in recent years further introduced zero-knowledge proof (zk-SNARK) technology, layering an additional mathematical proof on top of the Merkle tree that ensures "no single user's account balance is negative," preventing an exchange from offsetting one user's genuine shortfall against another user's inflated balance.

If I see an exchange publish Proof of Reserves, can I fully trust putting my assets on it?

No. What Proof of Reserves can guarantee has clear boundaries, and understanding those boundaries matters far more than simply seeing the "has done PoR" label. First, Proof of Reserves proves the asset position at one specific snapshot moment in time — it's not a continuous guarantee that solvency holds at every moment across all 365 days of the year. In theory, an exchange could temporarily borrow assets from a third party right before the snapshot and return them afterward (a tactic commonly called "window dressing") to make the numbers look good at that one moment, which doesn't mean the exchange's ordinary asset position is equally healthy. Second, most Proof of Reserves attestations only verify the asset side (how many crypto assets the exchange holds) and don't necessarily disclose liability-side details at the same time (whether the exchange carries undisclosed loans, derivatives exposure, or other off-balance-sheet liabilities) — a clean-looking proof of assets can't rule out the exchange simultaneously carrying other financial risks users have no visibility into.

The 2026 case of Polish exchange Zondacrypto is a concrete cautionary example: the exchange had previously published a Proof of Reserves, but its Hot Wallet reserves subsequently plunged by 99.7% at one point — an incident that clearly demonstrates that a single periodic snapshot-style proof of reserves isn't by itself sufficient to ensure safety; ongoing monitoring and more frequent verification matter just as much. Concrete indicators worth checking in practice include: whether the exchange has a reputable independent auditor publish Proof of Reserves regularly (rather than just once), whether the Reserve Ratio is maintained above 100% with some buffer (some exchanges publish an Overcollateralization ratio, such as 115% or 130%, as an extra safety Margin), and whether the exchange has any mechanism for disclosing liability-side information alongside its asset-side proof.