Nearly four years after FTX collapsed and wiped out customer funds, proof of reserves has become the industry's go-to confidence measure. Binance, OKX, Kraken and Crypto.com all publish some form of verification. But the checks are narrower than they appear, and they don't actually establish that an exchange can pay everyone back.
Why the industry moved to publish wallets
The push started right after FTX went under in November 2022. Binance founder Changpeng Zhao publicly urged exchanges to publish wallet evidence, and major platforms responded with dashboards, Merkle-tree tools and reserve ratios. The idea was to contain a trust crisis by letting customers verify their balances are included in the exchange's holdings. A Merkle tree does that: it lets a user confirm their account is part of the dataset without revealing other accounts.
Newer systems go further. Binance added zero-knowledge proof verification, using zk-SNARKs to confirm the math stays correct while keeping balances private. OKX publishes wallet addresses and downloadable proof files. Kraken offers account-level verification for covered balances. Crypto.com runs a Merkle-based verification interface.
What the reports don't say
Here's the catch: proof of reserves only shows that an exchange controlled certain assets at a certain moment. It doesn't prove solvency. Solvency requires a much deeper look at the company's obligations, ownership structure, and access to funds. A Merkle tree can authenticate records placed inside it, but it can't spot accounts that were left out before the tree was built.
It also can't see liabilities. Bank loans, tax bills, legal judgments, guarantees to affiliated companies — none of that shows up in a wallet snapshot. Reserve reports measure assets at a particular time and may be published only after an accountant or security firm finishes its work, so the snapshot might not even reflect the exchange's normal position.
The liability blind spot
Crypto exchanges have one advantage: much of what they hold sits on public blockchains, so the asset side is relatively transparent. The liability side is not. Liabilities are recorded across internal databases, bank accounts, contracts, and corporate ledgers, offering little visibility to outsiders. They include customer claims, fiat balances, derivatives, lending products, institutional loans, vendor bills, taxes, and legal claims across multiple jurisdictions.
That asymmetry is the core problem. An exchange can publish a clean Merkle tree and still be insolvent if its debts exceed its holdings. The industry hasn't yet found a way to give outsiders a real look at liabilities, and until it does, proof of reserves will stay a partial answer.
