Proof of reserves shows an exchange has the coins – so why doesn’t that prove it’s solvent?

Proof of reserves proves that an exchange controls a certain pile of crypto. It does not, in most implementations, prove that the pile is big enough to cover what the exchange owes its customers – and that second question, not the first, is what solvency actually means. An exchange can pass a proof-of-reserves check and still be insolvent if its liabilities exceed those verified assets, or if some of those assets are already pledged elsewhere.
Two separate problems, not one
According to crypto.news, in an article published 25 June 2026, a genuine solvency proof requires two things: proof of assets, showing what an exchange holds, and proof of liabilities, showing what it owes. The article calls the assets side “relatively straightforward,” because blockchains are public – an exchange can point to its wallet addresses or cryptographically sign a message from them, and anyone can check the balance sits there. Crypto.news calls the liabilities side “the hard half,” and illustrates why with a simple comparison: a billion dollars in verified crypto looks reassuring, but on its own says nothing about solvency if the exchange in fact owes its customers twice that amount.
The reason liabilities are harder to verify is structural, not incidental. What an exchange owes each customer sits in its own internal database, not on a public chain anyone can inspect. Proving that figure to an outsider means either trusting the exchange’s own books or building a cryptographic method – typically a Merkle tree or a zero-knowledge proof – that lets the totals be checked without exposing every customer’s individual balance.
What a Merkle-tree or ZK liability proof actually checks
According to crypto.news, Merkle trees and zero-knowledge proofs “help exchanges prove customer balances are included without exposing private account data.” The Cointelegraph reference-desk summary held here describes the same tools in similarly general terms, saying proof-of-reserves methods “like Merkle trees and zero-knowledge proofs” are used “to ensure transparency,” while still leaving liabilities unverified. Neither source, as held here, explains the technical mechanics of how either method works, and this page does not reconstruct that mechanism beyond what they state.
What such a check verifies, on the general logic of an inclusion proof – this page’s own reasoning, not a claim made by any source gathered here – is only what the exchange put into it in the first place. It cannot on its own confirm that every liability was included. A debt, a loan taken against customer collateral, or an obligation sitting off the exchange’s own platform could all sit outside the snapshot without the proof detecting the omission.
Timing raises a related gap. A snapshot taken and published on a given date says something about that date. According to Cointelegraph, proof-of-reserves audits “can verify asset holdings but do not account for liabilities,” which the outlet says can mislead users about an exchange’s actual solvency. Nothing in the mechanism itself prevents a liability from being added, or an asset from being moved out, the day after the snapshot is taken.
Encumbrance: the asset that isn’t really free
Even the easier half, proof of assets, has a quieter failure mode – though the clearest sourced example of it, in the evidence gathered here, concerns stablecoin issuers rather than exchanges. BitGo, in a blog post published 11 June 2026 about stablecoin proof of reserves, notes that reserves “may exist while still being pledged, restricted, or tied to other financial obligations.” A reserve asset disclosed by a stablecoin issuer can still be encumbered – posted as collateral, or otherwise restricted – while still appearing on a reserve snapshot as a free, available asset. Whether the same failure mode applies to centralized-exchange reserve snapshots specifically is not addressed by BitGo, which writes only about stablecoin issuers, or by any other source held here. BitGo also draws a distinction that matters when reading any published reserve report, exchange or stablecoin: a reserve attestation is generally “point in time,” performed by an accounting firm checking whether reported balances matched disclosed assets on a specific date, while a full audit is broader, testing internal controls and, depending on scope, liabilities and governance as well. The two are not interchangeable, per BitGo, even though both get called “proof of reserves” in public.
The worked example: FTX
The clearest illustration of why the liabilities half matters is the event that made proof of reserves a household term. According to crypto.news, in the article published 25 June 2026, FTX’s collapse in late 2022 revealed what the outlet calls “an estimated eight-billion-dollar hole” between what it claimed to hold and what it actually had. Crypto.news describes the underlying mechanism as one where customer account balances kept displaying on screen as though the funds were safe, while the exchange had funneled deposits to an affiliated trading firm that lost them. A proof-of-assets check on FTX’s visible wallets, on its own, would not have surfaced that shortfall, because the missing money was a liability problem – customers were owed more than the exchange actually held – not a question of whether any single wallet’s balance was real.
What this page does not tell you
This page cannot confirm whether any specific exchange operating today publishes a genuine, third-party-audited proof of liabilities, as opposed to a self-reported balance total or an asset-only snapshot; none of the sources gathered here name one. It cannot verify the accuracy of the shortfall figure crypto.news describes as an “eight-billion-dollar hole” beyond attributing it to that outlet’s own published estimate – the figure is not cross-confirmed against a court filing or a second outlet in the evidence used to write this page. The Block, in a piece we hold only as a headline, appears to describe a reserve-ratio formula and a threshold for it; because our access to that outlet is limited to the headline itself, this page does not state that formula or that threshold as confirmed fact. Separately, a Cointelegraph piece on whether reserve audits can prevent another FTX-like collapse is also held here as a headline only, so any quoted commentary reported to appear in that article is not repeated or attributed here. Finally, none of the sources gathered for this page explain how a liability snapshot is kept accurate in the gap between the moment it is taken and the moment it is published – the timing risk described above, and the specifics of what an inclusion proof can and cannot rule out, are this page’s own reading of the mechanism, not a claim any source makes explicitly.
Sources
Every fact above is attributed to one of these reports. Where they disagree, the article says so.
TheCoinrise reference desk
TheCoinrise reference desk (headline only)
TheCoinrise reference desk (headline only)
TheCoinrise reference desk
TheCoinrise reference desk
The post Proof of reserves shows an exchange has the coins – so why doesn’t that prove it’s solvent? appeared first on TheCoinrise.com.