Blast plans layer-2 wind-down with October 26 interface cutoff

Blast plans to wind down its Ethereum layer-2 network after concluding that maintaining the chain costs more than the revenue it generates. The project announced the decision on October 2 and asked users to move assets to Ethereum mainnet, turning an economic problem for the operator into an operational deadline for depositors and application developers.

The normal Blast interface is scheduled to support withdrawals through October 26. Blast says assets will remain withdrawable afterward, but holders will need to interact directly with its bridge contracts on Ethereum rather than use the standard interface. The distinction matters: October 26 is an interface cutoff, not a stated forfeiture or final redemption date.

Withdrawals will reopen in stages

According to Blast’s announcement, as reported independently by The Block and Decrypt, the project will first retrieve assets deployed through Lido. That process is expected to take approximately one week, during which withdrawals will be temporarily unavailable. The estimate is Blast’s operating timetable, not a guaranteed completion window.

After that process, Blast intends to reduce its withdrawal delay to 24 hours and reopen its normal withdrawal route until October 26. The team also said it would publish instructions for contract-based withdrawals before the interface cutoff. Those instructions were not available in the opened source record, leaving the precise post-cutoff procedure unresolved.

Blast’s public bridge page remained accessible when checked October 3 and still displayed deposit and withdrawal controls alongside promotional references to yield and points. The publicly rendered page did not confirm whether withdrawals were paused, when they would resume or whether deposits had been disabled. Users therefore should not interpret the presence of interface controls as proof that a transaction can currently be completed.

The bridge design makes the exit path consequential

Blast is an EVM-compatible optimistic rollup whose deposited assets can be deployed into external yield sources. L2Beat’s technical record identifies separate Ethereum contracts for the portal, standard bridge and yield managers, including a provider that routes ETH into stETH. That architecture explains why the operator says it must reclaim Lido assets before normal withdrawals resume.

The same record shows that Blast remains dependent on centralized operating roles. Only permissioned actors can post the state roots needed to finalize exits, and the contracts can be upgraded without a delay. L2Beat warns that withdrawals can freeze if the authorized proposer stops operating or if the bridge lacks sufficient liquidity while assets are being reclaimed from yield providers.

Direct contract access after October 26 consequently does not eliminate every operational dependency. It removes reliance on Blast’s normal website interface, but settlement still depends on the bridge system, valid state updates and adequate liquidity. The wind-down announcement does not establish when the sequencer, proposer or other infrastructure will cease operating.

Live measurements show continuing exposure

L2Beat displayed $32.61 million of total value secured in its October 3 snapshot and 5.15 user operations per second over the preceding day. Total value secured is L2Beat’s tracked valuation of assets associated with the network; it is not a count of customer balances, a measure of immediately withdrawable liquidity or an estimate of losses.

L2Beat also marked the project as undergoing impactful changes and warned that some technical information might be outdated. Its snapshot showed no ongoing liveness anomaly and normal tracked uptime over the preceding 30 days, indicating that the announced wind-down had not yet become a measured halt in data publication or state updates.

The remaining uncertainty is therefore about execution rather than the decision itself. Blast has declared that its economics are unsustainable, but it has not published audited revenue and expense figures, a final infrastructure shutdown date or the promised post-interface withdrawal guide. Those omissions prevent an independent assessment of the financial rationale and leave the full exit process subject to follow-up.