Proof of Reserves: What Exchange Reports Can and Cannot Show
Summary
The document introduces proof of reserves (PoR) as a way for centralized exchanges to show that reported reserves support customer balances. It describes reserve ratios, where a figure above full coverage is presented as a buffer, and connects increased PoR adoption to the trust concerns raised by the FTX collapse. It also explains Merkle trees as a method for checking user balances while limiting disclosure of individual account information, and mentions third-party audits as another verification approach.
The article discusses possible PoR coverage of staked ETH and suggests that changes in BTC and ETH balances may reflect user behavior. However, it supplies no specific report dates, exchange-level data, or methodology to substantiate these trends. A reserve snapshot alone does not establish a complete picture of liabilities or overall solvency, and the text does not explain the limits of its verification approaches. Its references to quantum threats are prospective rather than evidence of a present compromise.
Key ideas
- PoR reports aim to show whether exchange reserves cover customer balances.
- Merkle-tree proofs can enable balance checks while limiting disclosure of individual account details.
- Third-party audits are described as another way to validate reserve reports.
- Reserve ratios and asset-balance trends need context and do not, by themselves, establish an exchange’s full solvency.
- The document raises quantum computing as a future cryptographic concern without evidence of a current attack.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.