How Proof of Reserves Uses Audits and ZK Proofs for Exchange Transparency
Summary
The article outlines OKX’s Proof of Reserves program as a recurring way to let users and outside reviewers check whether reported exchange assets cover customer balances. It describes monthly snapshots, user self-verification, and independent review of asset ownership and coverage by Hacken. It also says the reports cover 22 assets and gives reserve ratios for several major tokens. The technical changes it highlights include zk-STARK checks, smaller proof files, and publicly available source code.
The document reports increased use of customer verification tools and describes a custody arrangement involving Standard Chartered in the European Economic Area, along with security certifications and monitoring systems. These are claims reported by the article; it does not explain the audit methodology in enough detail to independently assess its scope, liabilities, or limitations. Proof of Reserves can provide evidence about assets at a particular snapshot, but the text does not establish that it captures every obligation or guarantees solvency. Its figures and claims reflect the reporting period described and may change.
Key ideas
- Recurring reserve snapshots can give customers a way to check reported exchange assets.
- The article describes independent review of asset ownership and coverage alongside user verification.
- It reports using zk-STARK proofs and publishing code to support public scrutiny.
- A reserve snapshot alone does not establish the full scope of liabilities or guarantee solvency.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.