Stablecoin Depeg Risk for Treasury: The Plan You Need Before It Happens

The dangerous belief about a stablecoin treasury is "it's a dollar". It is a dollar until it briefly isn't — as the USDC/SVB episode showed. This article is narrower than the stablecoin treasury policy hub: it is specifically about one risk, depeg, and the two things that actually contain it — issuer diversification and a pre-decided contingency playbook. It explains what breaks a peg, why diversification caps the damage regardless of which issuer fails, and exactly what to decide before a depeg rather than during one.

The risk and the response

• A stablecoin can trade below par under stress. USDC/SVB is the clearest precedent: a portion of reserves at one bank, brief sub-$1 trading until access was resolved.
• Drivers: reserve quality and counterparty/banking concentration, amplified by opacity and market panic.
• Diversification through per-issuer limits is the single most effective treasury control — it caps the damage regardless of which issuer fails.
• The depeg contingency playbook must be pre-decided: detection, decision rights, actions, recording.
• GENIUS and MiCA reduce but do not remove depeg risk — a mitigant, not a guarantee.
• This pairs with the stablecoin treasury policy (which sets the limits) and reserve transparency.

The peg is not unconditional

The instructive precedent: around the Silicon Valley Bank failure, a portion of USDC's reserves was held at the bank, and USDC traded below one dollar briefly until access concerns were resolved. The lesson is not that a specific stablecoin is unsafe — it is that a reserve or counterparty problem can break a peg even for a well-regarded coin. A treasury that assumes the peg is unconditional has an unmanaged risk.

What drives depeg risk

• reserve quality — which assets back the coin, and how liquid and high-quality they are;
• counterparty and banking concentration — where the reserves are held;
• opacity — whether holders can quickly verify backing during stress;
• market panic — confidence can break before fundamentals do.

It is an issuer-and-reserves question (see reserve transparency), not a generic "crypto is volatile" one.

Diversification caps the damage

The single most effective treasury-level control is per-issuer concentration limits. They ensure no single issuer's depeg or freeze hits the entire position, turning a potential total liquidity loss into a bounded, survivable one. Diversification does not prevent a depeg — it caps the damage from any one, which is why it works regardless of which issuer has the problem (the policy control made concrete).

The contingency playbook

Pre-decided, because a depeg is fast:

Improvising during a depeg is how treasuries take avoidable losses. Decide while calm.

Regulation reduces, does not remove

US GENIUS and EU MiCA raise the floor on reserve quality and transparency for compliant issuers, lowering depeg probability but not to zero. A treasury still needs diversification and a contingency plan. Regulation is a mitigant, not a guarantee, and it is jurisdiction-specific.

Governance framework: operationalising depeg risk management

Understanding depeg risk is step one. Building the governance infrastructure to manage it in real time is step two:

Monitoring infrastructure:

• Designate a specific team member (or rotation) responsible for daily stablecoin price monitoring. In normal conditions this is a one-minute task; during stress events it becomes the most time-sensitive item on the treasury agenda.
• Set up price-threshold alerts for every held stablecoin issuer. The threshold should be below normal market noise (brief $0.001 intraday fluctuations are not depeg signals) but well above the point of serious concern. A common approach: alert at $0.995, escalate at $0.99, invoke contingency below $0.97.
• Subscribe to issuer reserve and operational communications channels. A banking counterparty issue or regulatory development at an issuer will often be publicly observable before the price reflects it.

Reserve quality assessment cadence:

• Conduct a full reserve quality review for each eligible issuer at least quarterly. The review reads the most recent attestation or audit, notes the reserve composition (what proportion is in cash vs short T-bills vs other instruments), and records any deterioration from the prior review.
• An issuer whose reserve quality has deteriorated below the policy threshold triggers a review of the concentration limit for that issuer — not necessarily an immediate exit, but a formal assessment with a documented conclusion.
• Reserve quality reviews are signed off by the treasury lead and filed with the audit records for the relevant period.

Contingency playbook testing:

• At least once per year, run a tabletop exercise: a scenario where one held stablecoin begins depegging during business hours. Walk through every step of the playbook: who gets notified, who makes the call, which system is used to execute the rotation, how the accounting entry is recorded, and how the board is notified. Identify gaps.
• After the exercise, update the playbook to address the gaps found, and re-file the updated version.

Accounting treatment for depeg events

A depeg event has specific accounting consequences that must be handled correctly, not deferred or averaged away:

• During the depeg (while holding the affected stablecoin): the holding is measured at its current market value, not its nominal $1.00 peg. If the functional currency is USD and the stablecoin is trading at $0.96, the holding is worth $0.96 per token. An unrealised measurement loss is recognised per the applicable framework.
• On disposal during a depeg (rotation or redemption at below-peg price): the realised loss is the difference between the carrying value at disposal and the proceeds received. This is a distinct accounting entry from the pre-depeg holding.
• Recovery to peg after a temporary depeg: if the stablecoin returns to $1.00 and the holding was not disposed of, the prior unrealised loss is reversed. Under fair-value accounting (where applicable), the position reverts to the recovered price. Confirm the reversal treatment with your accountant — it is framework-specific.
• Classification review: a stablecoin that has experienced a material depeg event, even temporarily, warrants a reclassification review — re-examine whether it remains appropriate to classify it close to cash, or whether its instrument risk has changed the appropriate balance-sheet line.

Practical guidance

1. Reject "it's a dollar" — the peg is conditional (USDC/SVB precedent).
2. Assess reserve quality and banking concentration per issuer.
3. Enforce per-issuer diversification limits — the damage cap.
4. Pre-decide the depeg playbook — triggers, authority, actions, order, recording.
5. Treat GENIUS/MiCA as mitigants, not guarantees.
6. Record depeg events and decisions in the audit trail; confirm approach with advisers.

How vendor tools support depeg management

Cryptio and Request Finance can surface per-issuer exposure and tag holdings for monitoring. Confirm the tool reports concentration against limits and retains the audit trail of any depeg-event handling. You cannot manage a risk whose exposure you cannot measure.

How Wag3s supports the plan

The diversification limits and the contingency calls are the treasury's to set and make. Wag3s Ledger supports the measurement and the record: it reports per-issuer stablecoin concentration against your treasury limits and records depeg-event detection and the decisions taken in the audit trail, so the diversification cap is measured and the playbook is evidenced rather than merely intended. See the Ledger product page and the Wag3s for accountants page.

Further reading

• Stablecoin Treasury Policy
• Stablecoin Reserve Transparency and Attestation
• The GENIUS Act and Stablecoin Treasury
• MiCA Stablecoins (ART/EMT)
• USDC vs USDT vs DAI for Treasury
• Stablecoin Treasury Accounting Controls

Sources

• USDC/Silicon Valley Bank episode — a portion of USDC reserves held at the bank; USDC traded below one dollar briefly until access concerns resolved (documented depeg precedent)
• Depeg drivers: reserve quality, counterparty/banking concentration, transparency/opacity, market panic
• Per-issuer diversification caps damage regardless of which issuer fails; pre-decided contingency playbook; US GENIUS / EU MiCA reduce but do not remove depeg risk (jurisdiction-specific mitigant)