A coverage ratio divides the resources an issuer holds against the obligations it owes, measured for the whole entity rather than for one position. Circle publishes the version most people have met: monthly attestation that it holds at least as much in dollar-denominated reserves as the USDC in circulation. In a token model the same shape gets applied to cumulative revenue against cumulative cost, testing whether the economy pays for itself across the full horizon. In both cases the number is a disclosure and a warning, not a trigger. Nothing gets liquidated at 0.99.
Coverage ratio and collateralization ratio get used interchangeably and are not the same measure. Coverage is entity-level and enforced by disclosure, by governance and eventually by a redemption run. Collateralization is position-level and enforced automatically by a liquidation at a published threshold.
Resources over obligations, for the whole entity
The general form is one line: what you hold, divided by what you owe. Above 1.0 the obligations are covered on paper. Below it they are not. What changes between versions is what you allow into each half of the fraction, and that is where the arguments happen.
The clearest real-world statement of the reserve version is Circle's own. In its post on the monthly USDC attestation, Circle describes publishing monthly reserve reports with attestations from an accounting firm, Grant Thornton at the time of that post, to give independent confirmation that it holds at least as much in dollar-denominated reserves as the amount of USDC in circulation.1 That is a coverage ratio with a target of at least 1.0, a stated numerator, a stated denominator, an attestor and a cadence. Anyone publishing one should be able to fill in the same four fields, and since the named firm and the cadence can change, read the live transparency page rather than a write-up of it.2
Why this is not a collateralization ratio
A collateralization ratio measures one position: the value of the collateral a specific borrower posted, divided by the debt that collateral secures. It is enforced by code. Cross the protocol's liquidation threshold and the position is closed by a liquidator, automatically, without anyone deciding to act. The consequence lands on one borrower and the ratio is recomputed every block.
A coverage ratio measures an institution. It is enforced by an attestation cycle, by counsel, by governance, and if it slips far enough, by every holder trying to redeem at once. Nobody liquidates the issuer at 0.98. The consequence is a run, and it arrives with a delay and then all at once. Same word shape, different unit of analysis, different failure mechanism, so keep the two names apart in your documentation and see the collateralization-ratio entry for the lending-side measure.
The modelled version, and how to read it
Inside a simulation the same fraction gets used on flows rather than stock. Cumulative revenue divided by cumulative cost, over whatever horizon the model runs, answers whether the economy pays for itself. Cost here means the whole obligation, including the token-denominated ones that founders often leave out: emissions issued to reward participants, market-making commitments, redemption promises, security budget.
Read it across percentiles, never at the median. A model whose median coverage is 1.4 and whose fifth-percentile coverage is 0.6 is a design that works in most simulated worlds and cannot pay in the bad ones. The median is the number that goes in the deck. The lower percentile decides whether you need a treasury policy.
1.0 is a composition question, not a safety line
A ratio of exactly 1.0 says nothing about whether obligations can be met when they are called. Two structures can print the same number and behave nothing alike, because coverage is a value comparison and redemption is a timing problem. Reserves in overnight instruments and reserves in something that takes a week to sell look identical in the numerator.
The same applies to the modelled version. Cumulative coverage above 1.0 is fully compatible with running out of money in month fourteen and recovering in month thirty, which is the front-loaded business model pattern, and the cumulative line will not show it. Put the monthly series next to the cumulative one every time.
What to settle before you publish one
Four decisions, in writing, before the first report goes out. What is in the numerator, valued how and how often. What is in the denominator, including obligations not yet due. Who attests, on what cadence, and what the gap between attestation dates means for a holder. And what happens the moment it drops below target: who is told, what mechanism fires, whether anything is contractually required at all.
That last one is usually blank, and the blank is the finding. A ratio with no consequence attached is a reporting habit rather than a control.
Common questions
What is the difference between a coverage ratio and a collateralization ratio?
Coverage is measured for a whole entity: reserves or revenue against the obligations that entity owes. Collateralization is measured for one lending position: posted collateral against the debt it secures. The enforcement differs more than the arithmetic. A collateralization ratio has an automatic liquidation threshold; a coverage ratio has an attestation cycle, a governance response and, if it slips far enough, a redemption run.
What is a good coverage ratio for a token project?
There is no universal number, and any figure quoted without its definition attached is noise. What matters more than the level is the composition and the timing: what counts as a resource, whether it can be realised at the speed obligations arrive, and what the ratio looks like in the worst tenth of simulated paths rather than at the median. Set a target, then define what happens when it is breached.
How is a coverage ratio used in a token simulation?
As the main viability output. The model divides cumulative revenue by cumulative cost, with cost including token-denominated obligations such as emissions and reward commitments, and reports the ratio across percentiles rather than as one figure. Coverage above 1.0 at the median and below 1.0 in the lower tail is a common and revealing result: the design works in normal conditions and cannot pay in adverse ones.
See Tokenomics Audit for how this applies in practice.
Sources
- New Levels of Detail in the Monthly USDC Attestation
Circle
Circle's own statement of the reserve coverage standard: monthly attestation confirming reserves at least equal to USDC in circulation, with the attesting accounting firm named in the post. - Transparency and Stability
Circle
Current entry point to the monthly attestation reports. Read this for the live cadence and attestor rather than relying on any secondary description.
Last reviewed 2026-08
Know the terms but not sure how they apply to your project? That is what an engagement is for. We design, document, and stress-test the whole token economy inside the Tokenomics Data Room.
100+ projects advised. Complete tokenomics in 4 to 6 weeks.