> For the complete documentation index, see [llms.txt](https://docs.enzyme.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enzyme.finance/onyx-user-documentation/enzyme-vault/overview/networks.md). # Networks An ***Enzyme Vault*** can be deployed on any EVM-compatible chain, but each Vault exists on a single chain. {% hint style="info" %} **About Networks** \ While strategies can be executed across any chains and systems through the ***Management Wallets***, the Vault Network defines on which chain deposits and redemptions take place. Funds deposited into the Vault smart contract can be transferred to the ***Management Wallet*** on that chain. **From there, it is up to the manager to handle bridging or off-ramping should they need to move assets outside the network.**\ \ Learn more about Funds Transfer [HERE](https://enzyme-finance.gitbook.io/onyx/enzyme-vault/subscription/funds-transfer). {% endhint %} --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.enzyme.finance/onyx-user-documentation/enzyme-vault/overview/networks.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.