Ethereum Layer 2 Blast shuts down with $51 million in user funds locked by five keyholders

• $51 million in user funds remain bridged to Ethereum, with $46.6 million staked as ETH through Lido.
• Blast’s fraud-proof system never fully activated, allowing a malicious state proposer to finalize invalid records and cause losses.
• Five keyholders control the shutdown contracts; any three can instantly pause withdrawals or alter contract code with no delay.

• $110 Daily chain revenue, down from $2.24 billion peak deposit value in June 2024.
• 99% Collapse in total value locked, from peak to $32.3 million as of announcement date.
• October 26 Final deadline for users to withdraw via Blast’s standard interface before direct contract interaction required.

According to reporting on the shutdown, Blast announced on Friday (October 2, 2026) that it will cease operations after determining operating costs exceed revenue with no path to viability. The network, an EVM-compatible Optimistic Rollup built by Blur marketplace founder Tieshun Roquerre (known as Pacman), invested user deposits into DeFi protocols to generate yield, a model that worked initially but became economically unsustainable.

Blast’s fraud-proof system design creates potential vulnerability with $51 million at risk

According to L2BEAT’s safety assessment, Blast’s fraud-proof infrastructure, designed to allow independent verification of state transitions, never fully activated. The chain relies on a single proposer to submit state roots to Ethereum; if that entity is malicious, it can finalize an invalid state without detection, creating direct loss-of-funds risk.

This design failure becomes critical at shutdown. The $51 million trapped in Blast’s contracts sit in a system with no working challenge mechanism. Users cannot independently prove that a withdrawal request is being blocked by malice rather than legitimate technical constraints.

The bulk of locked capital, $46.6 million, is staked ETH held with Lido, an interest-bearing staking service. Blast must unstake this position first, a process that takes approximately one week before bridge liquidity becomes available for withdrawal.

Five-person security council can pause withdrawals with no delay or timelocks

L2BEAT’s audit flagged that five keyholders collectively control the upgrade and withdrawal functions on Blast’s main bridge contract. A supermajority of three can instantly execute code changes or halt withdrawals without any delay (noted as CRITICAL risk in the assessment).

This stands in contrast to better-governed Layer 2s that impose timelocks, mandatory waiting periods before sensitive upgrades take effect, giving users time to exit if they disagree with a change.

Blast’s design places no such protection between a council decision and execution.

October 26 deadline forces users to interact directly with Ethereum contracts

Blast has set October 26 as the final date users can withdraw through the standard Blast application interface. After that date, users must interact directly with Blast’s smart contracts on Ethereum, a process requiring more technical knowledge and exposing users to the risk of signing unverified transaction data.

The week-long Lido unstaking period means the earliest bridge liquidity will arrive around October 9, after which the 24-hour standard Ethereum exit wait applies. Users who miss the October 26 deadline will still be able to withdraw, but only through manual contract interaction.

Blast joins a growing list of failed Layer 2 launches in 2026, including Lisk’s blockchain shutdown and the Bitcoin Layer 2 Botanix, both of which onboarded users rapidly before collapsing.

The CCS read. Blast’s shutdown underscores that venture-backed Layer 2s betting on yield generation without durable fee revenue lack a sustainable model. The custody risk during wind-down, unvetted fraud proofs and no timelocks on security council actions, reveals why institutional investors should demand governance safeguards similar to Arbitrum’s timelocked upgrades before depositing capital into early-stage rollups.

The key question unresolved: whether Blast’s five keyholders will publish full transparency on the withdrawal process as Lido’s unstaking completes. Standard practice would include cryptographic proof that funds remain unpaused and that no unauthorized state root finalization occurred during the unstaking window. Watch for this documentation by October 10; its absence would signal elevated risk for the $51 million still in the system.