Audit sprint Proof of reserves checklist
Use this checklist to separate useful reserve evidence from narrow attestations, old snapshots and marketing claims that do not show the full risk picture.
Review framework
Proof of reserves is useful only when readers can understand what was checked, what was excluded and how current the evidence is. The goal is not to create a trust badge; it is to map the source trail behind reserve-related claims.
Check whether claimed assets are tied to visible wallets, current balances or a credible attestation process.
A reserve claim is weaker if it does not explain which wallets, chains or asset categories are included.
A point-in-time snapshot can become stale quickly if update cadence is unclear.
Reserve assets matter less if the page does not explain how liabilities are represented.
Asset-only disclosures can overstate transparency if customer liabilities are missing or only partially represented.
Hidden debt, margin balances or internal loans can change the meaning of a reserve ratio.
Find who reviewed the evidence, what standard was used and what the review did not cover.
An auditor name alone is not enough; readers need the exact scope and limitations.
Exclusions are often more important than headline reserve ratios.
Check whether users can verify inclusion without exposing sensitive data.
A user-facing verification path makes the claim more reviewable than a static marketing statement.
If only technical users can understand the proof, the transparency value is limited.
A reserve page should show whether transparency is ongoing or a one-time response to pressure.
Regular updates are stronger than a single old snapshot.
Users need to know how discrepancies, paused withdrawals or chain issues are disclosed.
Reserve language should not imply more certainty than the evidence supports.
A reserve page can be useful while still being misleading if landing-page claims overstate the audit.
Proof of reserves does not automatically prove solvency, governance quality, liquidity or operational resilience.
Red flags
Reserve transparency is useful when it shows limits clearly. RisqScan treats missing caveats as a review signal, not as a reason to repeat a stronger claim.
FAQ
Proof of reserves is a transparency process that tries to show whether a crypto platform holds assets corresponding to customer balances or stated obligations. Its usefulness depends on scope, liabilities, update cadence and source clarity.
No. Proof of reserves does not prove an exchange is solvent. It may show a useful reserve snapshot, but solvency also depends on liabilities, liquidity, debt, governance, operational controls and excluded risks.
A useful reserve page should disclose wallet attestations, asset coverage, liability methodology, auditor scope, exclusions, update cadence, report dates and a user verification path when available.
Teams can use it to improve reserve pages, trust centers, risk disclosures and AI-citable source-backed content before publishing stronger transparency claims.
