USDC depeg, March 2023
Silicon Valley Bank failed on a Friday. $3.3B of USDC reserves were stuck inside it. You have 60 hours to defend the peg.
By Solomon Ajayi · Free to read, no signup
You're a treasury engineer at Circle on Friday March 10 2023. Federal regulators have just shut down Silicon Valley Bank, the second-largest bank failure in US history. Circle is one of SVB's largest depositors. The USDC stablecoin promises 1:1 backing by reserves, and $3.3B of those reserves are now frozen inside SVB while the FDIC sorts out depositor claims. Crypto Twitter has not noticed yet, but they will by morning. The team has the weekend before US markets open Monday to verify exposure, communicate, process redemptions from non-SVB reserves, and shore up confidence that USDC will hold its peg. Every choice you make here actually happened. Some were right calls. Some were rushed.
The decisions, beat by beat
Friday 10 March 2023, 16:00 UTC
FDIC press release: Silicon Valley Bank shut down by California regulators. Circle holds reserves at multiple banks; SVB is one of them. Treasury Slack lights up. Before any public statement, you need to know exactly how much USDC reserve cash is stuck inside SVB right now. The reconciliation has to be EXACT, guess wrong and the next 48 hours go very badly.
What's the first move?
✓ Pull the SVB sub-account balance and reconcile to the ledger
Right. Before any communication, you need ground-truth exposure. Verifying the SVB sub-account against your reserve ledger gives you the number you'll be defending all weekend.
Tweet that USDC is fully backed
Premature. You don't know the exposure yet. Tweeting reassurance you can't back up, that's how Terra-Luna died.
Wire all of Circle's cash out of SVB right now
Too late. The FDIC seized the bank at the start of business, wires are frozen and have been for hours. The cash is stuck until the FDIC releases it.
Issue an emergency mint to top up reserves
That's backwards. Minting more USDC increases your liability while reserves are frozen. It widens the gap.
Reconciliation complete: $3.3B confirmed frozen at SVB
The query against the reserve ledger lands. SVB sub-account: $3.3B, frozen as of FDIC seizure. BNY Mellon: $13.4B liquid. T-bills: $23.3B at 1-3 day notice. The number you'll defend all weekend is now in front of you.
Saturday 11 March 2023, 08:00 UTC
Crypto Twitter has figured it out overnight. USDC is trading at $0.95 on Coinbase and dropping. The market is pricing in panic. Silence is being read as confirmation of the worst. You need a public statement, and the WORDS matter, overclaim and you lose credibility when reality lands; underclaim and the depeg accelerates.
What does the statement say?
✓ Confirm the SVB exposure number, restate that all USDC remains redeemable 1:1
Right. Tell the truth: yes there's exposure, here's the size, but the redemption mechanism still works because the non-SVB reserves cover ongoing redemptions. Specificity beats vagueness.
Deny any exposure to SVB
Lying on a Saturday morning Twitter thread. The truth comes out by Sunday and your credibility is gone forever. This is what killed Terra.
Stay silent until Monday
Silence on a weekend market is read as panic. USDC drops further while you wait. By Monday the question is whether USDC survives, not whether the peg holds.
Promise to make depositors whole from Circle's own capital
Circle's own capital is a fraction of the SVB exposure. You can't promise what you can't deliver, and the moment that math gets done publicly the trust evaporates.
Public statement: SVB exposure confirmed, peg defended
Tweet thread + blog post: $3.3B at SVB, $36.7B at other custody points, redemption mechanism continues to operate against the non-SVB reserves. Specificity calms the market more than reassurance ever could. USDC stops the slide and stabilises at $0.92.
Saturday 11 March 2023, 15:30 UTC
A whale (a market-maker desk) is redeeming $500M of USDC right now. They need the dollars to hedge other positions over the weekend. If the redemption fails, the market reads that as proof the peg cannot hold. If it succeeds, you've just proven the redemption rail still works, but every cent goes out of the BNY Mellon balance, not SVB, and you need to GROUND that money move in the ledger to keep audit clean.
Post the journal entry for the $500M redemption.
✓ Burn $500M USDC (liability down), pay out from BNY Mellon (non-SVB asset down)
Correct. The liability shrinks because tokens are burned; the asset that funds the payout is the unfrozen BNY Mellon balance, not the frozen SVB cash. The two sides balance and the 1:1 invariant holds for what remains.
Burn $500M USDC, debit the frozen SVB cash account anyway (paper move)
You'd be claiming you paid from money you cannot actually access. The auditor catches it; the regulator catches it; the SVB recovery doesn't even match.
Refuse the redemption until SVB unfreezes
That's the failure mode you're trying to prevent. The whole point of holding 50%+ of reserves OUTSIDE SVB is so redemptions keep flowing while one custody bank is offline.
| Account | Debit | Credit |
|---|---|---|
| USDC Outstanding (Liability) (2300) | $500,000,000.00 | |
| Reserves: Cash at BNY Mellon (1711) | $500,000,000.00 |
Tokens Issued (liability) DOWN $500M; BNY Mellon cash (asset) DOWN $500M. Two-line entry; both sides shrink by exactly $500M and the invariant holds for the post-burn supply.
Sunday 12 March 2023, 22:00 UTC
Joint statement from Treasury / Fed / FDIC: all SVB depositors will be made whole, above the $250K FDIC cap, starting Monday morning. The frozen $3.3B is effectively guaranteed to come back. USDC trades back toward $1. You've defended the peg. Now you have to update the ledger to reflect the reclassification, the SVB cash is no longer 'frozen', it's 'pending FDIC settlement', recoverable within days.
How do you reflect the Treasury backing in the ledger?
✓ Reclassify SVB cash from 'frozen' to a recoverable receivable; no liability change
Right. The dollars are coming back at 100 cents. The SVB asset stays on the balance sheet at full value; only its disclosure footnote changes. USDC outstanding is unchanged because no minting / burning happened.
Mint $3.3B of USDC to celebrate the rescue
Minting tokens without new reserve cash inflow breaks the 1:1 invariant. The Treasury statement didn't create new cash, it just made existing cash recoverable.
Write down the SVB cash to zero, take a $3.3B loss
Overcautious. The Treasury announcement makes the cash recoverable in days. Writing it down would understate reserves, fail the next attestation, and trigger a separate panic.
SVB cash reclassified: frozen → pending FDIC settlement
Internal disclosure footnote updated: the $3.3B at SVB stays on the balance sheet at full value, recategorised as a near-term receivable expected to be made whole. No token mint, no token burn. The next attestation report will show this footnote change without restating reserves.
Monday 13 March 2023, 14:00 UTC
USDC trades at $1.00 again. The crisis is over. The post-mortem starts. Three engineering follow-ups are on the table; only one of them addresses the root failure mode.
Which post-mortem action gets prioritized?
✓ Diversify banking partners; cap any single bank at < 10% of reserves
Right. The root cause was concentration risk: 8% of reserves in one bank was already too much. The fix is structural, no single bank custody point can ever take the peg down again.
Add more colorful charts to the monthly attestation report
Cosmetic. The attestation report wasn't the failure mode. It correctly reported the SVB exposure on the day it happened. The problem was the exposure existing, not the reporting of it.
Move all reserves into a single mega-bank to simplify reconciliation
Exactly the wrong lesson. Consolidating into one bank takes single-bank concentration risk from 8% to 100%. Next failure becomes existential, not survivable.
Switch the stablecoin to fractional reserve to earn more yield
That would mean abandoning the 1:1 invariant entirely. The peg survived because the redemption mechanism worked from non-SVB reserves; fractional reserve would have made it impossible to honor redemptions.
Post-mortem: diversify banking partners, cap any single bank at < 10%
Treasury policy change ratified: no single custody bank holds more than 10% of total reserves; banking-partner diversification accelerated through Q2 2023. The peg held, the redemption rail held, the lesson is that 8% in one bank was already concentration risk and the next event won't tolerate even that.
What actually happened
USDC depegged from $1 to a low of $0.87 on Saturday March 11 as the market panicked. Circle confirmed Sunday March 12 that $3.3B was indeed stuck at SVB, about 8% of the $40B reserve. The US Treasury, Fed, and FDIC issued a joint statement Sunday evening guaranteeing ALL SVB depositors would be made whole, regardless of the $250K FDIC insurance cap. Monday morning USDC traded back to $1.00. Circle's post-mortem pushed the team to diversify banking partners aggressively, and the BUSD and DAI ecosystems took permanent reputational damage from contagion. The mechanics you just simulated, process whale redemptions from non-SVB reserves while you negotiate the SVB recovery, are exactly what kept the peg from collapsing further.
Play it from the engineer's seat
Reading the replay is one thing. Sit in the chair, make the calls live, and watch the consequences land in a real ledger. Free.