> 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.md).

# Multichain Ecosystem

Both weETH and eBTC are available across multiple chains via LayerZero. Users can natively mint these assets on L2s and alt-L1s directly in our dapp, then immediately use them in DeFi applications or bridge to other supported chains.

Some chains, such as Arbitrum for weETH, utilize canonical bridges. These canonical bridges only support transfers between Ethereum Mainnet and the specific L2 network, with no direct L2-to-L2 bridging supported. When using the bridge tab in our dapp, the network selector will automatically redirect you to the appropriate official bridge interface for your selected chain.

Note: Canonical bridge weETH deployments are separate from LayerZero-enabled chains. Users must use each chain's official bridge interface when working with these deployments.

* [Cross Chain Native Staking](/etherfi/get-started/multichain-ecosystem/cross-chain-native-staking.md)
* [How to Bridge weETH](/etherfi/get-started/multichain-ecosystem/how-to-bridge.md)
* [How to Bridge eBTC](/etherfi/get-started/multichain-ecosystem/how-to-bridge-ebtc.md)
* [Arbitrum Canonical Bridging](/etherfi/get-started/multichain-ecosystem/arbitrum-canonical-bridging.md)
* [weETH Bridge Deprecation](/etherfi/get-started/multichain-ecosystem/weeth-partial-bridge-deprecation.md)


---

# 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.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.