TrustDex › Guides › Stablecoin depeg risk
Stablecoin depeg risk: what backs the peg, and what breaks it
"Stable" is a design goal, not a law of nature. Every peg is a machine with moving parts — and each kind of machine has its own way of coming apart.
Traders treat stablecoins as the cash drawer of crypto: the thing you sell into, the unit you count profits in, the half of the pair you don't think about. That habit is exactly why depeg risk deserves study. When the asset everyone assumed was the safe leg breaks, it breaks portfolios that never consciously took the bet. This guide explains how the major peg designs are held together, how each one has historically come apart, what the earliest warnings look like on-chain, and why a depeg treats holders and liquidity providers very differently.
Check the stable leg too
Paste any token address — including the "safe" one — for a structural read.
Three machines for holding a dollar
Every peg is maintained by an arbitrage loop wrapped around some form of backing. Fiat-reserve stablecoins hold dollars and dollar-like instruments — bank deposits, treasury bills — with an issuer who promises one-to-one redemption. Overcollateralized crypto designs lock volatile assets worth more than the stablecoins issued against them, with liquidation bots enforcing the buffer when collateral falls. Algorithmic designs back the peg mostly with a mechanism: typically the right to swap one stablecoin for a dollar's worth of a sister token that the protocol mints on demand.
In all three, the peg holds because deviation is profitable to correct. Trade below a dollar and arbitrageurs buy the discount and redeem at par; trade above, and they mint at par and sell the premium. Understanding this loop is the key to the whole topic, because every depeg in history reduces to the same event: the arbitrage loop jammed — the backing was doubted, the redemption path clogged, or the mechanism ate itself.
Each design fails along its own seam
Fiat-reserve coins fail through trust and plumbing. The reserves live off-chain, so holders can't verify them directly; they rely on attestations, and on the issuer's banks staying solvent and cooperative. Doubt about reserve quality, a banking partner seizing up, or a regulator freezing accounts can all stall redemptions — and a redemption promise that stops being instant stops defending the peg.
Overcollateralized designs fail through collateral crashes and cascade mechanics. The buffer protects against ordinary volatility, but a violent, fast crash in the collateral asset can outrun liquidations, especially when the network is congested at exactly the moment everyone needs it. If liquidations clear at bad prices, the system can end up undercollateralized, and the stablecoin trades at the market's estimate of what's actually left backing it.
Algorithmic designs fail through reflexivity. The death-spiral pattern is well documented: the stablecoin slips, holders redeem into the sister token, the protocol mints more of it, its price falls under the new supply, which means the next redemption mints even more, and the mechanism that was supposed to absorb selling pressure instead amplifies it. Once confidence cracks, the design converts a small depeg into a total one with remarkable speed. Several of the largest collapses in crypto history followed precisely this script.
| Peg design | What holds it | How it breaks |
|---|---|---|
| Fiat-reserve | Off-chain dollars + issuer redemption | Reserve doubt, banking failure |
| Overcollateralized | Excess crypto collateral + liquidations | Crash outruns the buffer |
| Algorithmic | Mint/burn against a sister token | Reflexive death spiral |
| Bridge-wrapped stable | All of the above + a bridge's custody | Bridge hack or freeze |
The wrapped-stable trap: two ways to break at once
A stablecoin that reaches your chain through a bridge carries a second, independent failure mode. The wrapped version isn't the issuer's coin — it's a bridge's IOU for the issuer's coin, redeemable only while the bridge's locked collateral exists and its operators function. If the bridge is exploited, the wrapped stable depegs no matter how sound the original remains, because the claim behind it just became unbacked. Holders of a bridge-wrapped dollar are long two things at once: the peg design and the bridge's security. Our bridge-wrapped custody guide unpacks that second exposure in full; here it's enough to say that "which USDC is this, exactly?" is a question with real money riding on it.
Early tells: where a depeg shows up first
Depegs rarely arrive unannounced; they leak into market structure before they hit the headline price. The single most readable tell is pool imbalance on stable-swap pools. These pools are built to hold peer stablecoins in roughly even proportion, so when one side balloons — the pool filling up with coin X as everyone dumps it for its neighbors — the market is voting with its exits while the price still reads near a dollar. The skew often moves hours before the visible break.
The second tell is redemption friction. Anything that slows the par-redemption loop weakens the peg's defense: paused withdrawals at the issuer, sudden KYC hurdles, banking-hours delays becoming banking-days delays, a bridge queue backing up. Watch also for a widening spread between venues — when the issuer still quotes par but open markets quote less, the market is pricing the probability that redemption won't hold. None of these tells is proof on its own; together, moving the same direction, they're the closest thing depegs have to a siren.
Rule of thumb: a peg's health isn't its price, it's the balance of its biggest pools and the speed of its redemption path. Price is the last thing to move, because arbitrageurs defend it until the moment they can't.
Why the "boring" side of the pair still deserves a scan
Scanning the stablecoin leg of a trade feels like checking whether water is wet — which is exactly the complacency impersonators and copycats exploit. A scan settles that you're holding the canonical asset and not a same-name imposter or a wrapped variant you didn't mean to buy, and it surfaces the structural facts stablecoins legitimately carry: an active freeze authority (standard for regulated issuers, and worth knowing about before your funds sit in it), the mint's ownership, the token standard in use. On the EVM side it reads whether the contract is upgradeable and who controls it. Thirty seconds of reading the "boring" half of your pair is cheap insurance on the asset you plan to park everything in.
Holders versus LPs: the same break, very different bills
For a plain holder, a depeg is a simple markdown: the balance is intact, each unit is worth less, and the decision is whether to exit at a loss or wait for a recovery that may never come. Painful, but linear.
For a liquidity provider, the same event is convex in the wrong direction. A pool containing the failing coin becomes a magnet for it: arbitrage sells the depegging asset into the pool and pulls the sound assets out, so the LP's position slides toward being one hundred percent the broken coin, acquired at progressively worse implied prices. Providing stable-pool liquidity is, in effect, writing insurance on every peg in the pool — the fees are the premium, and a depeg is the claim. That's a perfectly legitimate trade to make, but it should be made knowingly, and sized like an insurance book rather than like a savings account.
Know exactly which dollar you're holding
Scan it, confirm the issuer and standard, then swap non-custodially with your keys.
Frequently asked
What actually keeps a stablecoin at one dollar?
Arbitrage against a redemption promise. If one token reliably redeems for one dollar of backing, traders profit by correcting any deviation, and those trades pull price back to par. Every depeg is a break in that loop — doubted backing, clogged redemption, or a mechanism with nothing real to redeem.
Which stablecoin design is the riskiest?
Purely algorithmic ones have the worst structural failure mode: defending the peg means minting more of a sister asset that's collapsing at the same time. Fiat-reserve coins concentrate risk in the issuer and its banks; overcollateralized designs are exposed to collateral crashes. Different shapes of failure — none risk-free.
What are the earliest depeg warning signs?
Stable-swap pools tilting hard toward one coin — the market dumping it against peers — plus redemption friction: paused withdrawals, banking trouble, or a widening gap between issuer par and open-market price. These usually move before the headline price does.
Is trading a few tenths of a cent under the peg already a depeg?
Not by itself — stablecoins wobble within a narrow band constantly. What matters is behavior under stress: snapping back quickly means the arbitrage loop works; drifting wider as volume grows means real doubt. Judge depth, duration, and pool-balance trend, not a single tick.
Do LPs lose more than holders in a depeg?
Usually. A holder eats the price drop on their balance. An LP's pool fills up with the failing coin as arbitrage drains the sound ones, so the position converges toward being almost entirely the broken asset. Stable-pool LPing is selling peg insurance — fees are the premium, a depeg is the claim.