Proof of Reserves: check what the evidence actually covers
Proof of Reserves can provide evidence about selected assets and customer balances at a specified time. It is not automatically a financial-statement audit, proof of overall solvency or a guarantee that withdrawals will remain available.
Your task: read one reserve report and write down its date, scope, account-inclusion result and the questions it leaves unanswered.
Separate three different questions
Are the assets controlled?
Published wallet balances and control checks can support a claim about assets at a snapshot. A balance on a blockchain does not by itself show whether assets were borrowed, pledged or subject to another party’s claim.
Was your balance included?
A Merkle proof can demonstrate that a particular account record belongs to a committed dataset. Your successful check does not establish that every customer or every liability was included, or that the input records were correct.
Can the business meet its obligations?
That broader question needs information about liabilities, asset quality, legal claims, controls and access to funds. A high reserve ratio for one token does not answer it. Read the report’s engagement and limitations, not just its badge.
Inspect a report in three steps
Identify exactly what was examined
Start from the provider’s official site. Record the reporting entity, snapshot date, asset list and account types. Open the actual report: who performed the work, under what standard, and what procedures or assurance are stated?
Verify the matching account record
Use the provider’s documented verification process for that snapshot. Compare the included balances with your records at that time, allowing for the report’s treatment of margin, staking or other products. Never supply a private key or recovery phrase to verify reserves.
Write down the remaining gaps
Check whether the report addresses other liabilities, encumbered assets and changes since the snapshot. If an asset or account is absent, establish whether it is excluded or incorrectly recorded. Preserve the report date and ask support a specific question; do not turn missing evidence into a positive conclusion.
Worked example: a ratio needs a denominator
A fictional platform reports 105 BTC against 100 BTC of included customer balances: its stated ratio is 105%. If another 10 BTC obligation was excluded, the same assets cover only 105 ÷ 110, or about 95.45%, of those combined obligations. This arithmetic does not prove that any real platform omitted liabilities. It shows why scope matters. Asset restrictions, borrowing and priority claims would require further analysis even if the ratio exceeded 100%.
Three false conclusions to avoid
“Verified” means everything was audited
Verification can cover a narrow assertion or agreed procedures. Read the exact engagement, criteria and conclusion. An accounting firm’s name alone does not turn a reserve report into a full financial-statement audit.
Today’s balance must match an old snapshot
Later deposits, trades and withdrawals change your balance. Compare against the snapshot timestamp and supported products. A difference needs investigation in context; it is not automatically proof of fraud or proof that nothing is wrong.
Inclusion proves instant access
A valid inclusion proof does not guarantee operational withdrawals, insurance or your legal recovery position. Combine it with custody terms, withdrawal information and independent evidence about the provider.
Try it: what does your check establish?
Your 0.4 BTC balance appears in a valid proof dated one month ago. The report covers BTC and ETH spot balances only. You also hold USDT in an earn product. What can you conclude?
Show the reasoning
You have verified inclusion of the stated BTC record in that snapshot. The check says nothing about your USDT earn balance, later changes or all company debts. Find the earn product’s terms and relevant evidence separately; do not label the whole account fully covered.
