Reserve Attestations
Understand stablecoin reserve attestations, point-in-time assurance, scope, liabilities, audit differences and the limits of proof-of-reserve style disclosures.
Reading progress — saved on this device
Reserve attestations provide third-party or issuer-published evidence about specified reserve balances at a stated date, helping users evaluate whether reported assets correspond with token liabilities.
What it is
An attestation is an assurance engagement over specific information and criteria. In the stablecoin context, it may report whether selected reserve balances equal or exceed specified outstanding token liabilities at a point in time.
The usefulness of an attestation depends on who performs it, the standard used, the information tested and what is excluded. A narrow confirmation of bank and custody balances can be valuable evidence while still leaving material questions about the wider issuer.
How it works
A typical process may compare token supply or specified liabilities with bank, custodian or securities-account balances. Assets may be categorised and valued according to defined criteria.
Frequency matters. Monthly evidence leaves gaps between reporting dates; even daily snapshots do not prove that assets were continuously present or unencumbered unless the engagement specifically addresses those questions.
Liability completeness is critical. Confirming £10bn of reserves is not enough if the relevant liabilities are larger or if other claims rank ahead of token holders. The engagement must clearly define what liabilities were compared.
Legal availability is another separate question. An asset can exist in a custody account but still be subject to liens, restrictions or an insolvency structure that affects token-holder access.
How to analyse it
Read the report from the scope section outward. Do not stop at a headline “100% backed” statement; identify the date, criteria, accounts, asset categories, liabilities and explicit limitations.
| Question | Why it matters | What to verify |
|---|---|---|
| What date/time? | A snapshot can become stale quickly. | Reporting date, frequency and publication lag. |
| What assets are in scope? | Excluded or broadly labelled assets can change risk. | Accounts, instruments and valuation criteria. |
| What liabilities are in scope? | An incomplete denominator can overstate coverage. | Token supply, pending redemptions and other relevant claims. |
| What assurance level? | Different engagements provide different evidence. | Attestation standard, practitioner opinion and exclusions. |
A reserve attestation can materially improve transparency, especially when frequent, detailed and independently performed. But it should complement—not replace—analysis of legal structure, custody, redemption and issuer governance.
Comparing reports through time can reveal changes in reserve composition. A stable headline coverage ratio can mask a shift from cash toward assets with more duration or counterparty risk.
Worked example and thought exercise
A report states that £5.05bn of reserves support £5.00bn of tokens at month-end, implying 101% coverage. The report excludes other issuer liabilities and says nothing about reserve encumbrance between reporting dates.
The correct conclusion is narrow: at the stated time, specified in-scope assets exceeded specified in-scope token liabilities under the report’s criteria. It is not evidence that the entire company was solvent at all times.
Thought exercise: How would your confidence change if the next report still showed 101% coverage but the cash share fell from 70% to 10% while longer-duration assets rose sharply?
Common mistakes and practical workflow
- Calling every reserve attestation a full audit.
- Ignoring the reporting date and publication lag.
- Looking only at reserve assets without checking the liability definition.
- Assuming existence of assets proves token holders have a direct or bankruptcy-remote claim on them.
Practical workflow
- Read the practitioner’s scope, criteria and opinion.
- Record the exact reporting date and publication frequency.
- Reconcile in-scope liabilities with outstanding token supply methodology.
- Inspect reserve composition and valuation rules.
- Combine the report with legal, custody and redemption analysis.
✅ Knowledge checkpoint
- Why is a 101% attested ratio not proof of continuous solvency?
- What risk arises if the liability denominator is incomplete?
- How does a reserve attestation differ from a full financial-statement audit?
- Why should reserve composition be tracked across successive reports?
FAQs
❓ Is an attestation the same as an audit?
No. A reserve attestation is generally narrower and tests specified information and criteria rather than the full financial statements.
❓ Does an attestation prove assets are unencumbered?
Only if the engagement specifically addresses encumbrance or legal availability.
❓ Why does publication frequency matter?
Because issuer balances and token supply can change between reporting dates.
❓ Can an attestation still be useful?
Yes. It can provide important independent evidence when its scope and limitations are understood.
📋 Summary
Reserve attestations are valuable transparency tools but should be interpreted narrowly. Their strength depends on scope, frequency, liability completeness, asset detail and the type of assurance provided.
Want this in a personalised order?
Take the crypto assessment and get a custom path of 10 modules matched to what you already know. Free, no card required.
Build my path →