A Depeg Isn’t a Probability Question, It’s a Timing Question

If you’re the product owner, risk lead, or evaluating whether to issue a stablecoin—answer one question first: tomorrow morning your coin depegs, what are your first three moves? Can’t answer, and you’re not ready to run a money business.

Most people imagine a depeg as a probability question—”will it happen.” Wrong. For a dollar business running 24/7, a depeg is a timing question: which day, what hour, who picks up the phone first, who has the authority to hit pause. The teams that treat it as a probability question prepare a “hopefully-never-needed” document; the teams that treat it as a timing question prepare a process that “might run tonight.” And the reality is brutal: a team that’s never drilled it—its first depeg is usually its last.

The Framework: The Depeg Runbook

Break a depeg into five sequential action clocks:

Detect (who sees it first) → Stop the bleed (which valve to close first) → Communicate (what to say, to whom) → Pay out (in what order to release money) → Post-mortem (turn the autopsy into the next product version).

It draws as a crisis timeline: the X-axis is minutes, the Y-axis is the actions and owners each of these five lines should trigger. If the “five deaths” of pegs is pathology, this runbook is the ER procedure.

Most Teams’ Crisis Plan Is a PDF Nobody Has Opened

Counterintuitive judgment: most issuers’ “emergency plan” doesn’t fail to exist—it’s just never actually been run once. Banks have stress tests and fire drills; stablecoin teams often have only a compliance-mandated document gathering dust in a shared drive. When the first depeg actually hits, nobody knows who can pause the contract, who the reserve bank’s emergency contact is, or whether the support script should say the word “redemption.”

The minimum action is a “tabletop exercise”: pick one death (say, the reserve bank blowing up), run all five clocks blackout-style, and log every spot where things “stall, have no owner, wait for the boss to decide.” The output of a drill isn’t confidence—it’s a list of breakpoints. Confidence lies to you; a breakpoint list doesn’t.

I have firsthand memory of “what’s most missing in that moment.” Building HPB, we hit an on-chain security incident that needed urgent coordination. What was most missing wasn’t a technical fix—technical problems always have someone who can solve them—it was the pre-agreed “who can decide, and who can we reach in minutes.” What truly burns money isn’t the fix itself, it’s the minutes spent “waiting for someone to approve.” A stablecoin depeg is the isomorphic lesson: the most expensive thing in a crisis is always the decision vacuum.

Five Clocks: The First 60 Minutes After a Depeg

The crisis is won or lost in the first hour, and that hour is about pre-defined owners and thresholds, not on-the-spot cleverness:

• Detect: who, on what metric, triggers an alert at how many standard deviations? (Price deviation threshold, sudden pool-depth drop, redemption-queue length.) The point—don’t be the last to learn of your own depeg, from Twitter.
• Stop the bleed: which valve first? Pausing minting and pausing redemptions are opposite signals—pausing redemptions is nearly a public admission of insolvency and lights the reflexive stampede; use with extreme caution.
• Communicate: silence is the most expensive choice. Set a hard rule—first statement within 30 minutes, template pre-written, lawyer pre-reviewed. The market fills every minute of your silence with the worst-case ending.
• Pay out: release money by a “liquidity waterfall”—cash/short-dated first, slow assets later, not first-come-first-served smashing through the pool.
• Post-mortem: open the autopsy doc the day of, while the signals are still hot.

Suicide Switches Buried at the Design Stage

Counterintuitive opener: many stablecoins aren’t killed by the market—they buried themselves a suicide switch at the design stage. These look like “flexible” and “efficient” in a bull market, and all detonate in reverse during panic:

• Backing reserves with your own token or a strongly correlated asset (UST/LUNA’s cause of death);
• Uncapped, single-sig minting authority—handing the printing press to one key;
• Writing “high yield” into the product promise, subsidized by new inflows (the passive-interest road regulators are closing in on);
• Multisig threshold too low, time-lock missing in governance—an attacker or insider can rewrite the rules within one block;
• Multi-chain issuance with supply that doesn’t reconcile—one bridge failure depegs every version at once.

One judgment to close: design a stablecoin’s governance assuming one of your key people gets bought, not assuming everyone’s a good actor. The good-actor assumption is fine in a bull market and will kill you the day things go wrong.

The Product Owner’s Must-Answer Checklist

Before the first line of code, before the first distribution deal, a product that can’t answer the below shouldn’t launch. This compresses the whole book into one page, grouped by its five through-lines:

• Redemption (trust): T-plus-what payout? Who can cap redemption amounts? Worst-case instant-liquidity coverage ratio?
• Reserves (profit): counterparty concentration cap? Single-bank exposure red line? Who audits monthly disclosure, and to whom is it public?
• Distribution (growth): could channel revenue-share-backflow be deemed “paying interest”? Where’s the single-channel dependency red line (think Circle’s reliance on Coinbase)?
• Compliance (boundary): which slot am I on the regulatory spectrum—licensed, gray, censorship-resistant? Do I have freeze/blacklist capability, and is it compliant?
• Crisis (this chapter): who runs the depeg runbook? How often is it drilled? Is the first public-statement draft written now?

One judgment: a product owner who can’t answer “tomorrow it depegs, what are my first three moves” isn’t ready to run a money business.

Others face a depeg on luck and adrenaline; you face it with a runbook you’ve run ten times—a crisis creates no winners, it only reveals who was already ready.

That plan on your team—when was the last time anyone opened it?

—— From The Stablecoin Operating Manual: Distribution, Reserves, and Compliance, Chapter 18

Sources (verified):

• UST/LUNA reflexive collapse from self-backing reserves (May 2022, public record); Circle-Coinbase distribution structure (verified against Circle’s Q1 2026 10-Q, same source as Chapters 7/10): https://www.sec.gov/Archives/edgar/data/1876042/000187604226000150/crcl-20260331.htm; GENIUS Act issuer interest ban (Public Law 119-27, 2025-07-18).
• GENIUS Act redemption constraints (verified): §4 requires public redemption policy and fee disclosure; discretionary limits on timely redemption may only be imposed by qualified regulators; §7 permits redemption limits under unusual and exigent circumstances.
• CLARITY Act (H.R.3633): passed House 2025-07-17, pending in Senate, not law; the “ban passive yield, keep activity rewards” distinction is a proposed direction, not settled text.