Bible Network Crypto DeFi Onchain RWA AI Agent Stablecoin Chain SAFU CryptoTax DeFAI AGI Claude Me Claude Skill Claude Design Claude Cowork
Independent Media
Not affiliated with any project
The Deepest Crypto Knowledge Base
crypto-bible.com
LATEST
Perpetuals Enter US Regulated Markets: Kraken Launches CFTC-Compliant Perps via Bitnomial as Kalshi Led and Coinbase Followed  ·   ·   ·   ·  World (WLD) Enters Simple Plan Phase 3: From Token Subsidies to World ID Fees — How AI-Era Proof-of-Human Infrastructure Plans to Make Money  ·  MiCA Deadline Hits in Days: 75% of EU Crypto Firms May Lose Authorization, Millions of Users at Risk of Cutoff
Glossary · onchain-data

Proof of Reserves (PoR)

onchain-data Advanced

30-Second Version · For the impatient
Proof of Reserves (PoR) is a transparency mechanism used by cryptocurrency exchanges or custody institutions to prove to users and the public that they genuinely hold the corresponding reserves for all user assets. FTX's collapse (November 2022) revealed the enormous risks of exchanges misappropriating user assets, driving industry-wide adoption of Proof of Reserves. Technically, PoR typically combines a Merkle tree with verifiable on-chain addresses: placing all user account balances into a Merkle tree, allowing any user to verify their balance is included in the total reserves, while the exchange's on-chain addresses' holdings can be independently verified.
Full Explanation +
01 · What is this?

What is the technical implementation of Proof of Reserves, and how does Merkle tree protect user privacy while providing verifiability? PoR's technical core is the Merkle tree — a cryptographic data structure letting you prove a specific account is included in a total asset list without exposing other users' balances. Specific PoR implementation steps: First, the exchange builds a complete Merkle tree using all user accounts (account ID + balance) as leaf nodes, computing the Merkle Root. Second, the exchange publicly publishes this Merkle Root hash and the on-chain addresses holding the corresponding assets (independently verifiable by anyone on blockchain explorers). Third, users can request their account's Merkle Inclusion Proof from the exchange — the set of hash values needed from their account to the Merkle Root, letting users independently compute the reconstructed root hash and confirm it matches the exchange's published root hash, verifying their account is genuinely included in the total. Privacy protection advantage: each user can only see their own Merkle path (a few hash values), with no visibility into other users' balances.

02 · Why does it exist?

How did FTX's collapse drive the adoption of Proof of Reserves, and could PoR have prevented FTX's problems? FTX's collapse (November 2022) is one of the most severe trust crises in crypto industry history, directly driving PoR to become the industry transparency standard. What happened at FTX: FTX, without informing users, transferred user assets deposited at FTX to affiliated trading firm Alameda Research; Alameda used these funds for high-risk investments and lending. When markets crashed and Alameda's investments failed, FTX's user deposits couldn't be fully covered; FTX collapsed within three days with over $8 billion in user funds lost. Could PoR have prevented FTX: theoretically, if FTX had implemented genuinely rigorous PoR, users could verify at any time whether their balances were still included in FTX's total reserves, and independently verify whether FTX's claimed on-chain holdings matched total user balances — any discrepancy could be detected early. But in practice, PoR isn't foolproof: FTX actually published a reserves report days before its collapse, but it was flawed — it may have included collateral (FTT tokens themselves), with incomplete liability disclosure. Genuinely effective PoR requires simultaneously revealing both assets and liabilities, not just assets.

03 · How does it affect your decisions?

What are PoR's known limitations, and what problems can't it solve? Even with a complete and technically correct PoR, several problems remain unresolved. First, liability invisibility: PoR shows how much the exchange holds, not how much the exchange owes. If an exchange holds $1 billion in Bitcoin (PoR-verifiable) but also owes $2 billion in loans (not disclosed in PoR), it remains insolvent — this is the essence of FTX. Second, PoR timing limitation: PoR is a snapshot at a specific time; exchanges can borrow large amounts briefly before publishing PoR to temporarily bolster reserves, returning it after the audit — flash loan style reserve manipulation. Third, auditor independence: PoR audit quality depends on whether the executing institution is genuinely independent and capable — if the auditor has close commercial relationships with the exchange, audit credibility is discounted. Fourth, user action delay: even if PoR reveals problems, by the time users detect issues and can actually withdraw, the exchange may have implemented freezes — PoR doesn't guarantee funds can be withdrawn when problems are discovered.

04 · What should you do?

How can you use existing tools to verify an exchange's Proof of Reserves, and does verification require technical knowledge? The PoR verification process is more intuitive than imagined — several tools make it relatively easy. Exchange's own PoR page: Binance, OKX, Kraken, and other major exchanges provide PoR query pages; after logging in you can see: which Merkle tree leaf node your account is at; the Merkle path from your node to the root hash; and on-chain addresses of claimed holdings. Self-verification on-chain: if you have doubts about the exchange's UI, you can take the major wallet addresses the exchange publishes and directly query balances on BTC/ETH blockchain explorers (Blockchain.com, Etherscan), independently confirming these addresses actually hold the claimed amounts. Nansen, Arkham Intelligence: these platforms track known addresses of major exchanges, aggregating views in one interface. Technical barrier: basic PoR verification (confirming your account is included in the total) requires no technical knowledge; but deep analysis (investigating potential liabilities, evaluating audit completeness) requires stronger financial and on-chain analysis skills.

Real-World Example +

Use Binance's PoR system launched after FTX's collapse to illustrate the actual verification flow. Weeks after FTX's collapse in November 2022, Binance launched its Proof of Reserves system under industry pressure and user demand. At binance.com/en/proof-of-reserves, after logging in you can see your account's position in the Merkle tree and corresponding hash path. The system shows Binance's claimed total holdings of BTC, ETH, BNB, and other assets, along with corresponding major on-chain addresses — you can directly query these addresses' balances on Etherscan or Bitcoin blockchain explorers, independently confirming Binance's claims. After 2023, Binance regularly updates PoR data; in the 2026 version, PoR also includes Reserve Ratio displays, showing each asset's reserves relative to user balance liabilities (all >100%). This process lets ordinary users without technical background complete their own account inclusion verification in minutes — a level of transparency no centralized institution in traditional finance (banks, brokers) can provide.

Diagram
Proof of Reserves: Merkle Tree Verification Flow儲備金證明驗證流程圖:三個方塊呈現 PoR 的核心架構——①交易所(藍色):把所有用戶的帳戶餘額放入默克爾樹,公開發布根哈希;②用戶(橙色):向交易所請求自己帳戶的默克爾路徑,可自行驗證帳戶餘額被包含在總儲備金中;③審計師(綠色):獨立核實交易所的鏈上地址確實持有對應的聲稱資產。圖底說明 PoR 能證明和不能證明的兩個Proof of Reserves: Merkle Tree Verification FlowExchangePlaces all userbalances inMerkle treePublishes root hashUserRequests MerkleProof of theirown accountVerifies inclusionAuditorVerifies on-chainwallet addressesactually holdtotal claimed BTCWhat PoR Proves vs What It Doesn't✓ PROVES: Your balance is included in total✓ PROVES: Exchange holds claimed on-chain assets✗ DOESN'T PROVE: No hidden liabilities✗ DOESN'T PROVE: Solvency at all timesCrypto Bible · crypto-bible.com
Feel free to share. Please credit the source.
Common Misconceptions +
✕ Misconception 1
× Misconception 1: An exchange with PoR is safe; I don't need to worry about its solvency. Wrong. As noted, PoR only proves asset existence, not the absence of hidden liabilities — an exchange with $1B in assets but $2B in liabilities can still pass PoR's asset-side audit. PoR is a necessary transparency tool but insufficient as the sole safety guarantee. Judging exchange safety also requires considering: regulatory compliance status, whether there's an insurance fund, whether user funds are separated from company funds (segregated accounts), and whether it's regulated in multiple jurisdictions.
✕ Misconception 2
× Misconception 2: The data on PoR publication day is valid long-term; a PoR report from a month ago is still meaningful. Wrong. PoR is a snapshot at the publication time; an exchange's financial position can change significantly in a short period. Effective PoR should be continuous (regularly updated), not one-time. If an exchange only has one PoR report from months ago without regular updates, that report's current validity is very limited.
The Missing Link +
Direct Impact

Proof of Reserves' core trade-off is between providing an unprecedented transparency standard and being only the starting point of transparency, not the endpoint. In traditional finance, no bank or broker allows users to verify in real-time that their assets genuinely exist — PoR brought this transparency to the crypto industry, a real advancement. But PoR only solves half the transparency problem: it shows asset existence but doesn't fully show financial health. The real solution requires a Verifiable Balance Sheet — simultaneously disclosing both assets (already achieved by PoR) and liabilities (currently universally not fully disclosed by PoR). The crypto industry is pushing PoR 2.0 concepts (cryptographically disclosing liabilities as well) and independent third-party continuous auditing — but these are still in early development stages, still some distance from truly mature transparency standards.

Ask a Question
Please enter at least 10 characters