USDC / SVB Depeg (2023)
See the evidence before you trust the verdict.
Historical Investigation
This investigation covers the 2023-03-10 to 2023-03-13 event window and is frozen at peg restoration. USDC remains a live, actively traded asset; nothing here is a statement about its current condition. Evidence reflects on-chain state and public disclosures during the window.
On March 10, 2023, Silicon Valley Bank was closed by its regulator, and Circle disclosed that $3.3B of USDC reserves were held there. Over one weekend, the largest "fully reserved" stablecoin traded near $0.88, DAI followed it down through its own USDC collateral, and Curve's 3pool inverted as holders fled to USDT. The peg was restored not by market forces but by information: the March 12 federal guarantee of SVB deposits. This investigation reconstructs the window because it demonstrates two things every stablecoin holder should internalize - a stablecoin is a credit exposure to its reserves and banking rails, and composability transmits that credit risk across DeFi in hours.
Confidence per domain, not a single score.
Incident
Attribution
Loss
Recovery
How the incident unfolded
March 8-9, 2023
Banking stress builds
Silvergate announces voluntary liquidation; SVB discloses large securities losses and a failed capital raise. Deposit flight from SVB accelerates. None of this is yet visible in the USDC peg.
Public disclosures and regulatory record
March 10, 2023
SVB closed; Circle discloses $3.3B exposure
California's regulator closes SVB and appoints the FDIC as receiver - the second-largest US bank failure at the time. After banking hours, Circle discloses that $3.3B of USDC reserves sit at SVB. The weekend redemption gap begins.
Regulator closure record; Circle disclosure, 2023-03-10
March 11, 2023
The depeg prints on-chain
USDC trades to roughly $0.88 on major DEX pools. Curve's 3pool inverts as holders exit USDC and DAI into USDT. DAI falls to roughly $0.89 through its PSM dependency. Several venues pause USDC-USD conversions pending banking clarity.
On-chain pool prices and composition (verified in evidence table)
March 12, 2023
Federal guarantee announced
Treasury, the Federal Reserve, and the FDIC jointly announce all SVB depositors will be made whole. The peg begins recovering within minutes - the market was pricing information, and the information changed.
Joint federal statement, 2023-03-12; on-chain price response
March 13, 2023
Peg restored, redemptions resume
Circle confirms reserve access; redemption rails reopen with the banking week. USDC returns to $1.00. Net redemptions run heavy in the following days as holders de-risk - the event ends, the repricing of stablecoin risk does not.
On-chain price data; issuer statements
What the evidence shows
Reserve exposure
$3.3B of reserves at SVB
Issuer disclosure by Circle, 2023-03-10, subsequently consistent with the federal resolution. Provenance: disclosure, not independent audit.
Peg deviation
Low ~$0.88 on 2023-03-11
On-chain DEX pool prices (Curve, Uniswap) during the window; deviation visible across venues.
Redemption rails
Paused over the banking weekend
Direct redemption settles through banking rails, which do not operate on weekends - the exit everyone priced was temporarily unavailable.
Contagion path
DAI followed to ~$0.89
DAI was heavily collateralized by USDC via MakerDAO's Peg Stability Module; the dependency transmitted the depeg mechanically.
Resolution trigger
Federal deposit guarantee, 2023-03-12
Joint Treasury / Federal Reserve / FDIC statement guaranteeing SVB depositors. Peg restored as redemptions resumed 2023-03-13.
Contract integrity
No exploit, no compromise
The USDC contract operated normally throughout. This was a reserve-credibility event, not a technical failure.
What XemaS found
The event began off-chain. On Friday, March 10, 2023, Silicon Valley Bank was closed by the California regulator and placed into FDIC receivership. That evening, Circle disclosed that $3.3B of USDC's roughly $40B in reserves was held at SVB. The disclosure landed after banking hours, at the start of a weekend - the exact window in which direct redemption of USDC for dollars does not settle.
On-chain, the response was immediate and measurable. Holders who could not redeem sold instead: USDC traded down to roughly $0.88 on major DEX pools on March 11, and Curve's 3pool - normally balanced across DAI, USDC, and USDT - inverted as traders dumped USDC and DAI for USDT. DAI, itself heavily backed by USDC through MakerDAO's Peg Stability Module, followed USDC down to roughly $0.89: a mechanical contagion, not a loss of confidence in Maker.
On Sunday, March 12, the Treasury, Federal Reserve, and FDIC jointly announced that all SVB depositors would be made whole. The peg began recovering within minutes of the announcement and was effectively restored by Monday, March 13, as Circle confirmed reserve access and redemptions resumed. No smart contract failed at any point; what failed, temporarily, was certainty about the dollars behind the token.
Where the value went
No funds were stolen; the flow was a rotation. With redemptions closed for the weekend, DEX pools became the only exit, and value rotated out of USDC and its dependents into USDT and volatile assets - then partially rotated back after the federal announcement. The measurable footprint is pool composition, not a theft trail.
| Step | Movement |
|---|---|
| 1 | Holders exit USDC via DEX pools (redemptions closed) |
| 2 | Contagion leg: DAI sold alongside USDC via PSM linkage |
| 3 | Rotation destination: USDT and volatile assets |
| 4 | Post-resolution: redemptions reopen, supply contracts |
Downstream impact
MakerDAO / DAI
The PSM's large USDC backing transmitted the depeg to DAI mechanically (~$0.89 low). Maker subsequently rebalanced collateral policy - the clearest protocol-level lesson of the event.
Curve 3pool
The primary on-chain venue of the run: pool composition inverted toward USDC/DAI as USDT became the scarce leg. The pool functioned as designed; its state is the event's best on-chain record.
USDC-denominated DeFi broadly
Lending markets, LP positions, and treasuries denominated in USDC repriced with the peg. No systemic failures resulted, but the weekend demonstrated how a single issuer's banking exposure propagates as market risk across the stack.
Who was involved
Circle (issuer)
Issuer of USDC. Disclosed the SVB exposure on the evening of the bank's closure; confirmed reserve access at resolution. Attribution is public and uncontested.
Silicon Valley Bank
Held $3.3B of USDC reserves at closure. Its failure - a banking event with no on-chain component - was the root cause of the depeg.
Treasury / Federal Reserve / FDIC
Issued the March 12 joint statement guaranteeing SVB deposits. The peg's recovery timestamp aligns with this announcement, not with any on-chain mechanism.
MakerDAO
Largest on-chain holder of USDC exposure at the time via the Peg Stability Module; DAI's depeg was a mechanical consequence of that collateral concentration.
Why it matters
A stablecoin is a credit instrument: you hold a claim on reserves you cannot see, settled through banking rails that keep business hours. The depeg priced exactly that - reserve uncertainty plus a closed exit. The recovery priced its removal. For position sizing, treat stablecoin exposure as issuer credit exposure, and treat weekend and off-hours windows as the periods when the redemption backstop is weakest.
Evidence table
| Fact | State |
|---|---|
| SVB closed and placed into FDIC receivership | VERIFIED |
| Circle reserve exposure disclosure ($3.3B at SVB) | VERIFIED |
| USDC traded to ~$0.88 low | VERIFIED |
| Curve 3pool composition inverted toward USDC/DAI | VERIFIED |
| DAI depegged to ~$0.89 via PSM dependency | VERIFIED |
| Federal joint statement guaranteeing SVB deposits | VERIFIED |
| Peg restored; redemptions resumed | VERIFIED |
| USDC contract compromise | VERIFIED |
What was not visible
Reserve composition rests on disclosure
XemaS did not independently audit Circle's reserves. The $3.3B figure and the ~$40B total are issuer disclosures, corroborated by the federal resolution but not by an on-chain proof. They are labeled with that provenance.
Off-chain and CEX flows are partially visible
Centralized-exchange order books and OTC flows during the weekend are not on-chain. The reconstruction here relies on DEX state, which was the venue of price discovery while redemptions were closed, but aggregate sell pressure across CEXes is not fully enumerable.
Exact depeg lows vary by venue
The ~$0.88 low is a representative on-chain figure; different pools and minutes printed different extremes. No single canonical low exists.
Counterfactuals are not evidence
Whether the peg would have recovered without the federal guarantee is unknowable. This investigation documents what happened, not what would have happened.
What this incident teaches
A stablecoin is a credit exposure with banking hours
"1 USDC = 1 USD" is a redemption promise that settles through banks. When the banks are closed - or failing - the promise and the market price can diverge. The weekend was not incidental to this event; it was structural.
Composability transmits credit risk in hours
DAI depegged without anything going wrong at Maker. Collateral concentration means your peg inherits someone else's reserve risk. Map the dependency graph before the stress event, because during it there is no time.
Recovery followed information, not intervention
No on-chain mechanism restored the peg. A federal statement did. Stablecoin risk assessment is therefore partly off-chain intelligence work - reserve composition, banking counterparties, disclosure velocity - and any tool that only reads the chain will miss the cause.
The contract working perfectly is not the same as the asset being safe
Every automated contract check on USDC passed throughout the event, correctly: nothing was exploited. Risk lived in the reserves. Scanners answer "is the code hostile?" - a necessary question that is not sufficient.
Scan any address with the same evidence engine
EVM, Solana, Bitcoin, and Tron. Every scan returns verified evidence, not a traffic-light score.
Scan a token or walletNo account required for a first scan.