Main Street's msUSD Loses 90% Value After Liquidation Cascade

Main Street Protocol’s decentralized stablecoin msUSD lost its dollar peg and effectively collapsed on June 20, 2026, after a rapid cascade of liquidations exposed severe collateral and liquidity imbalances on-chain. What happened On-chain contract logs and protocol state data point to sudden market volatility that destabilized the regional collateral pools backing msUSD. That shock produced deep liquidity gaps inside the protocol’s pools, triggering a sequence of liquidations that the system could not absorb—ultimately breaking msUSD’s peg. Scale of the damage Main Street’s own data show a dramatic impact: the protocol’s total value was roughly 1.1 trillion, with about 318 billion directly hit by the liquidity crisis. Reports indicate the stablecoin lost some 90% of its value during the event, underscoring how quickly stress can overwhelm DeFi risk mechanisms when market moves outpace protections. User impact and protocol response For msUSD holders, the depeg represented a significant loss of value and a clear failure of the asset to provide the stability expected of a stablecoin. Main Street’s team says its risk engine is actively working to stabilize reserves—a necessary first step for any recovery—but regaining user trust after a collapse of this magnitude is likely to be difficult and time-consuming. Why this matters to DeFi The incident highlights two core truths about decentralized finance: first, that complex collateral architectures can be fragile under extreme market pressure; and second, that public on-chain data make failures immediately visible and auditable. Observers and affected users will be watching Main Street’s mitigation steps closely; further transparency and clear remediation plans will be critical. Sources and attribution This story is based on smart contract logs published by Main Street Protocol and the protocol’s official statement on the event. Article by the News Desk, edited by Samuel Rae. For the primary logs, see Main Street Protocol Logs.