BLOCKCHAIN AI.NEWS

Infrastructure

Blast Put 16,148 stETH Into Lido's Exit Queue Within Hours of Its Shutdown Post

On October 2 the Ethereum layer 2 said the chain costs more to run than it earns and gave users until October 26 to leave through its interface. By 19:21 UTC the contract that backs every bridged ETH held no stETH and 21 Lido withdrawal requests, up from four two hours earlier. L2Beat's count of the canonical bridge fell from $49.7 million to $6.3 million in the same hour. The chain's revenue over the previous day was $110.

Editorial illustration: a vast frosted-glass reservoir standing almost empty, a faint high-water line etched far up its walls, and at its base a chrome drain valve lit warm gold through which a thin stream of silver coins slides into a narrow channel lit electric blue
✓ The Block had the announcement first among the outlets this desk found · Blast's yield manager read on Etherscan and sampled hourly by this desk through a public node · L2Beat and DefiLlama data · Cointelegraph, The Crypto Times, Bankless, KuCoin News · Lido and Blast documentation

Blast's announcement, posted to X on October 2 and reported by The Block at 12:54 p.m. Eastern, runs to a few sentences. "We launched Blast with the goal of building a self-sustaining chain for users and developers. Unfortunately, the economics of operating the chain no longer make sense." And: "The ongoing costs of maintaining Blast exceed the revenue generated by the L2, and we do not see a credible path to making the chain economically sustainable." Users are asked to move their assets back to Ethereum. They can use Blast's own interface until October 26. After that, Cointelegraph reports, the funds stay reachable but only by calling the bridge contracts on Ethereum directly, with instructions promised before the deadline.

The order of operations is the part worth reading twice. Blast said it would first unwind its position in Lido, a process it expects to take about a week, during which withdrawals are unavailable. Once that is done, the withdrawal delay drops to 24 hours. The desk checked whether the first step had started. It had, and it was nearly finished before most of the coverage was published.

What a Blast ETH is

Blast's pitch, from its November 2023 launch, was yield on the ETH you bridged without doing anything. The mechanism, in its documentation: "ETH yield from L1 staking, initially Lido, is automatically transferred to users via rebasing ETH on the L2." The ETH deposited on Ethereum does not sit in a bridge contract. It is staked through Lido and held as stETH in a contract Etherscan labels Blast: ETH Yield Manager Proxy, which L2Beat describes as the "escrow for ETH that is invested into yield-bearing contracts such as stETH." Stablecoins go a similar route into USDB, whose yield "comes from MakerDAO's on-chain T-Bill protocol." An ETH balance on Blast is, in other words, a claim on stETH held by that contract.

That design is why Blast's bridge was slow. When the chain opened for withdrawals on February 29, 2024, users discovered a 14-day wait, double the seven-day challenge period of comparable optimistic rollups. In July 2024 Blast cut it to seven days, and CryptoSlate's report on the change says the 14-day window had been designed to accommodate Lido withdrawals. The delay was a liquidity buffer. L2Beat's assessment makes the same point from the other direction: Blast's fraud proof system "is currently under development," users "need to trust the block proposer," and the project "is not even a Stage 0 project." A bridge whose delay exists to let Lido finalize can shorten the delay the moment the Lido position is gone. That is what Blast is doing.

Two hours on one contract

The desk read the yield manager's stETH balance and its count of Lido withdrawal-request tokens at two-hour intervals back to the evening of September 30, through a public Ethereum node. Lido's withdrawal queue issues an ERC-721 token, unstETH, for each request, representing "the right to claim underlying ether once the request is finalized." A single request is capped at 1,000 stETH; larger amounts must be split.

For two days nothing much happened. The contract held 16,277 stETH at 21:10 UTC on September 30 and 16,148 at 17:21 UTC on October 2, with the small decline spread over a handful of ordinary withdrawals of the kind that service users leaving the chain. It held between two and four unstETH tokens throughout. At 18:02 UTC on October 2, Etherscan shows a cluster of transactions on the contract with the method name Unstake. By the desk's next sample, at 19:21 UTC, the stETH balance was zero and the contract held 21 unstETH tokens. Seventeen new requests for 16,148 stETH is exactly what Lido's 1,000-token cap produces: sixteen full requests and one for the remainder. At the hour's ETH price on L2Beat's chart, about $2,684, the stETH moved was worth roughly $43 million.

L2Beat saw the same thing from its side. Its canonical-bridge figure for Blast, which counts assets in the project's escrow contracts, read $49.67 million at 18:00 UTC and $6.31 million at 19:00 UTC. Nothing left Ethereum. The stETH became a claim on Lido's queue, which L2Beat does not count as bridge collateral, and the queue will pay out ETH when Lido's oracle finalizes the requests. Lido's help page says that "normally takes between 1 - 5 days." Blast said about a week. After the move, Etherscan shows the yield manager holding about 1,466 ETH, worth around $3.9 million.

Blast's ETH Yield Manager, sampled by this desk

Time (UTC)stETH heldLido withdrawal requests
Sep 30, 21:1016,2772
Oct 1, 13:1416,2442
Oct 2, 01:1716,1512
Oct 2, 15:2016,1484
Oct 2, 17:2116,1484
Oct 2, 19:21021
Oct 2, 21:220.0221
Balances of contract 0x98078db0…C8FE read by this desk from Ethereum at the listed blocks; stETH rounded to whole tokens. Withdrawal requests are the contract's count of Lido unstETH tokens. Etherscan dates the Unstake transactions to 18:02 UTC on October 2.

What is left to run, and what it earns

The numbers on the other side of the ledger are small enough to state plainly. DefiLlama's fee data for the chain, read by the desk, puts Blast's revenue at $110 over the last 24 hours, $440 over seven days and $1,895 over 30. Its total value locked peaked at $2.26 billion on June 5, 2024 and stood at $32.0 million on October 1. L2Beat's broader value-secured figure was $37.9 million on October 2, and its page carries a warning that the BLAST token issued by the project itself accounted for 49 percent of it. The $2 billion that arrived in the months before the chain existed, which The Block and Cointelegraph both recall, came in on points and a promised airdrop and left when it could. Bankless put it in one line: incentives "can pull in capital fast, but they can't make it stay."

Two features of the exit are worth watching rather than assuming. First, L2Beat records that Blast's contracts are upgradable by two 3-of-5 multisigs with no timelock, which is what allows the withdrawal delay to be changed by configuration, and which also means the promise that funds remain accessible after October 26 is a promise about how those keys will be used. Second, the week in which withdrawals are paused is a week in which the collateral behind every Blast ETH is a Lido queue position rather than stETH. Lido's documentation says its oracle finalizes requests in batches against the ether available to it, and nothing in the record suggests a problem with these. It is simply a different thing to hold.

Blast is not the first layer 2 to close this year. Zerion's Zero Network told users in May to bridge out by the end of July, saying "maintaining a standalone blockchain was the wrong path" to what it was building. Blast is the largest to go, by what it once held, and the first the desk has seen whose closing instructions begin with another protocol's withdrawal queue.

The Take

Credit where it is due: Blast moved its users' collateral into Lido's queue within hours of saying it would, before the week it asked for, and left the step visible on-chain for anyone who looked. That is the right way to close. The detail worth keeping is what it reveals about the bridge delay. For two and a half years Blast's withdrawal wait was described as if it were a security property of a rollup. It was a liquidity property of a Lido position, and the day the position went away the delay went to 24 hours. Every chain that restakes its bridge deposits for yield has an exit that is two queues deep, its own and its yield source's, and the second queue belongs to someone else. Users should ask, while a chain is healthy, which contract actually holds their ETH and what it would take to get it back if the sequencer stopped. On Blast the answer was a contract labeled Yield Manager, and now 21 tokens that say Lido owes it money.

More on the subject