How Merkle Tree Proof of Reserves Verifies Exchange Assets
Summary
This announcement explains OKX’s monthly Proof of Reserves process and a dashboard update that shows how customer balances are calculated across BTC-, ETH-, and USDT-denominated products. Its described verification approach uses a Merkle tree so customers can check that their account balance is included in the exchange’s reported liabilities. The exchange then compares aggregate liabilities with balances in publicly visible on-chain wallets to support its reserve claim. The announcement also defines “clean” reserves as assets excluding the exchange’s own platform token and reports that OKX’s holdings met that definition.
The release reports $7.5 billion in BTC, ETH, and USDT reserves and says the exchange maintains 1:1 reserves; it also describes publishing wallet addresses for public review. These are company-reported figures and process claims, not an independent audit assessment included in the text. Proof of reserves can provide evidence about assets and user liabilities at a point in time, but the document does not explain its treatment of off-chain obligations, encumbrances, or completeness of liabilities. It is a transparency and custody-risk overview, not a trading strategy.
Key ideas
- A Merkle tree can let a customer verify that their balance appears in an exchange’s aggregate liability record.
- The described reserve check compares customer liabilities with assets shown in public on-chain wallets.
- The release reports 1:1 reserves and excludes platform tokens from its definition of clean reserves.
- Proof of reserves does not, by itself, establish that all obligations are disclosed or that assets are unencumbered.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.