Folio v0.9 — CEX + On-chain Consolidation is liveSee what's new →

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

Treasury·

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

A stablecoin can trade below par under stress — the USDC/SVB episode showed a portion of reserves at one bank was enough to break the peg briefly. Treasury depeg risk is managed with reserve-quality assessment, issuer diversification, and a pre-decided contingency playbook, not optimism.
Author avatar Wag3s TeamEditorial team specializing in Web3 finance, crypto tax, and DAO operations. Based in Zurich, Switzerland.

Reviewed by Wag3s Editorial Team — verified against the documented USDC/SVB depeg episode, issuer reserve-quality variation, and depeg-contingency best practice · Last reviewed May 2026

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. Depeg risk is not eliminated by picking a good coin; it is managed with diversification and a plan. This guide is that plan.

TL;DR

  • 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 resolved).
  • Drivers: reserve quality + counterparty/banking concentration; opacity and panic amplify.
  • Diversification (per-issuer limits) is the single most effective treasury control — it caps damage regardless of which issuer fails.
  • Depeg contingency playbook must be pre-decided — detection, decision rights, actions, recording.
  • GENIUS / MiCA reduce but do not remove depeg risk — a mitigant, not a guarantee.
  • Pairs with stablecoin treasury policy (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, how liquid/high-quality;
  • counterparty/banking concentration — where reserves are held;
  • opacity — if holders cannot 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: 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:

ElementDecide in advance
DetectionPrice thresholds, reserve-event news triggers
AuthorityWho is authorised to act
ActionsRotate issuer, redeem, hedge, pause stablecoin usage
OrderSequence of operations
RecordingEvent + decisions in the audit trail

Improvising during a depeg is how treasuries take avoidable losses. Decide 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 is jurisdiction-specific.

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 helps

Wag3s Ledger reports per-issuer stablecoin concentration against treasury limits and records depeg-event detection and the decisions taken in the audit trail — so the diversification cap is measured and the contingency playbook is evidenced, not just intended. See the Ledger product page and the Wag3s for accountants page.


Further reading

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)
Editorial disclaimer
This article is informational and does not constitute financial or investment advice. Depeg risk is real and issuer-specific. Confirm your treasury risk approach with qualified advisers.