> For the complete documentation index, see [llms.txt](https://etherfi.gitbook.io/etherfi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://etherfi.gitbook.io/etherfi/get-started/multichain-ecosystem/weeth-partial-bridge-deprecation.md).

# weETH Partial Bridge Deprecation

#### Overview

As part of hardening our cross-chain infrastructure, ether.fi is deprecating weETH bridging on a small subset of chains. Consolidating onto fewer, higher-activity chains reduces risk and allows us to focus security resources where they matter most.

#### Deprecated Chains

The following chains will have weETH bridging disabled on **June 30, 2026**:

**Scroll, Swell, Bera, zkSync, Mode, Blast, Morph, Sonic**

These were selected based on usage, TVL, and integration depth. Additional chains may be deprecated in the future based on the same criteria. Any future deprecations will be communicated with ample advance notice.

#### What You Need to Do

If you hold weETH on any of the deprecated chains, bridge it back to Ethereum or another supported chain before **June 30, 2026**.

#### After Deprecation

If you miss the deadline, recovery is still possible. Reach out to our support team and we'll process your recovery manually. A fixed fee of **0.5 weETH** applies to cover the manual handling.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://etherfi.gitbook.io/etherfi/get-started/multichain-ecosystem/weeth-partial-bridge-deprecation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.