Back to News

Swell shuts Ethereum Layer 2 chain early, warns users funds left after June 23 won’t be recovered

Swell closed its Ethereum Layer 2 chain earlier than planned, risking funds left after June 23 becoming unrecoverable. Users who still had deposits on Swellchain are affected because the platform’s support and access were cut off sooner than expected.
Swell, the liquid staking and restaking protocol, has pulled the plug on its Ethereum Layer 2 chain, Swellchain. The shutdown left users with a moving deadline that created real recovery risk.

The project first announced in April it would sunset the chain by June 15 to focus on its new product, Faro. But on June 16, Swell posted on X that the shutdown had already begun and assets left after June 23 would be unrecoverable. The homepage echoed that June 23 warning. The original blog had said withdrawals could still work via direct contract interaction until June 30 – though not recommended.

That date shift matters. Appchain shutdowns don't just turn off a switch. Frontend support disappears, wallet trackers stop updating, bridge access gets cut, and user attention evaporates. What started as a routine roadmap update turned into a ticking clock for anyone who still had funds on Swellchain.

Swell's reasoning: slower restaking growth and cheaper Ethereum transactions made Swellchain unnecessary. The Optimism Superchain L2 had been running since late 2024, but the market for restaking has cooled. Meanwhile, Ethereum's own fees have fallen so much that even Vitalik Buterin recently questioned whether most L2s still serve a purpose.

The project stressed that rswETH, swETH, and SWELL tokens on Ethereum mainnet are unaffected. But the chain itself – and any assets left on it past June 23 – is now a black hole. Users who missed the window may have no way to recover funds.

For crypto traders, this is a textbook reminder of appchain risk. Layer 2 chains can launch fast, but they can also vanish faster than the infrastructure around them. Swell's case shows that the real danger isn't the shutdown itself – it's the gap between what a team says in a blog and what actually happens when support collapses.

The key watch item now: whether any users who failed to bridge out by June 23 will manage to recover assets via direct contract calls. Swell said that path required technical expertise and was not recommended. For most retail users, it's likely already too late.