0x0e5d3d2b0e5d…0e5d3d2e
Blast to Wind Down Layer 2, Leaves $63.5M on Canonical Bridge
Blast will shut down its Layer 2 network, with about $63.5 million still parked in its canonical bridge and users given until Oct. 26 to withdraw through the standard interface.
Outputs
About $63.5 million remains in Blast's canonical bridge as of the report
Standard withdrawal interface closes Oct. 26
Contract-based withdrawals continue after Oct. 26
Shutdown attributed by the Blast team to unsustainable costs
The Defiant first reported the wind-down
Blast will shut down its Layer 2 network, leaving roughly $63.5 million in the project's canonical bridge and requiring users to pull assets out by Oct. 26, according to the Defiant's reporting.
The team attributed the closure to unsustainable costs, offering no operational timeline for the wind-down beyond the public-facing withdrawal cutoff. Contract-based withdrawals will continue after the Oct. 26 date, meaning technically proficient users retain a path to their funds even after the standard interface closes.
How much is left on the bridge?
About $63.5 million sits in Blast's canonical bridge, the canonical asset-pool contract that holds user deposits backing wrapped assets on Layer 2. The Defiant's headline figure implies material residual exposure for any user who has not yet initiated a withdrawal.
What changes on Oct. 26?
The Oct. 26 deadline governs the normal withdrawal interface only. Users who fail to act by that date forfeit the convenience path but do not lose on-chain recourse: contract-based withdrawals remain available, subject to whatever gas costs and technical friction the underlying smart-contract path imposes.
Why is Blast shutting down?
The team's stated rationale is unsustainable costs — a generic framing that, in Layer 2 economics, typically refers to the combination of sequencer operating expenses, data-availability or blob fees, and rollup-to-L1 settlement overhead failing to break even against fee revenue. The Defiant report does not specify which cost line drove the decision.
What happens to apps deployed on Blast?
The source does not detail treatment of native applications, smart contracts or the BLAST token. The shutdown leaves a set of operational questions for builders: whether migrations are planned, whether any successor operator will inherit the sequencer role, and how contract-level state will be preserved once the front-end interface is darkened.
The canonical-bridge balance and the two-track withdrawal architecture — interface-led by Oct. 26, contract-led thereafter — give users a narrow but explicit exit runway, pending any further operational guidance from the Blast team.
via The Defiant (Source)