A custodian may publish blockchain addresses, demonstrate control with signatures, and compare balances with selected customer obligations. Kraken describes a process that aggregates in-scope customer balances in a Merkle tree and lets individual customers verify that their balance was included in the snapshot. This is a useful example of combining public asset evidence with a customer inclusion check. The relevant questions remain specific: which entity, assets, customers, and timestamp does that particular report cover, and what procedures were actually performed?

A valid inclusion proof establishes a relationship to the published dataset; it cannot independently prove that the dataset contains every liability. In its March 2023 advisory, the PCAOB's Office of the Investor Advocate explained that proof-of-reserve engagements can omit liabilities, borrowing arrangements, and holders' legal rights. The advisory is a staff publication, not a Board rule. It also distinguishes these engagements from financial statement audits.

A reserve figure above the reported customer balance therefore should not automatically be read as a complete assessment of the business's financial condition.

A snapshot becomes historical as soon as assets move. It does not establish that funds remain available later or that operational controls will prevent future losses. Read the report itself, identify the provider and agreed procedures, and distinguish observed wallet balances from claims about ownership or freedom from encumbrances. As an editorial research checklist, retain the snapshot date, legal entity, included tokens, liability methodology, exclusions, and any customer verification steps alongside the headline result.

These details make comparisons more meaningful than a reserve-ratio badge alone.