> 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/administration-app/vault/subscription-management/cross-chain-enablement.md).
# Cross Chain Enablement
Cross-chain deposits allow users to deposit into your vault from a blockchain different from the one the vault lives on. The transfer between chains is handled by [Chainlink CCIP](https://chain.link/cross-chain), Chainlink's cross-chain interoperability protocol.
{% hint style="info" %}
A ***Cross-Chain Deposit*** is a deposit initiated on a chain different from the vault's home chain. The deposit asset is bridged via CCIP and settled on the vault's chain, where the depositor receives their shares.
{% endhint %}
### Enabling Cross-Chain Deposits
Cross-chain deposits are configured from your vault's **Advanced Configuration** under the **Cross Chain** tab. Each chain you enable here becomes a source chain that your users can deposit from. Users connected to any enabled chain will see it as an option on the deposit form.
#### Adding a Source Chain
Navigate to **Vault → Configure → Advanced → Cross Chain**. Click the **+** button to open the chain picker, select the chain you want to enable, and confirm. The chain becomes available to depositors immediately.
{% hint style="warning" %}
Before enabling a new source chain, verify two things in the official [Chainlink CCIP Directory](https://docs.chain.link/ccip/directory):
* The **lane** between the source chain and your vault's chain is active.
* Your vault's **deposit token** is supported on that lane (has a CCIP token pool registered for the pair).
If either is missing, depositors will see an "asset cannot be bridged" message and will be unable to deposit from that chain.
{% endhint %}
#### Removing a Source Chain
To stop accepting new deposits from a chain, remove it from the list. Removal only blocks **future** deposits from that source — it has no effect on what has already happened.
{% hint style="info" %}
Removing a chain does **not** cancel pending cross-chain deposits already in flight; those continue to settle normally. Depositors who already hold shares minted from past cross-chain deposits can still redeem them as usual, regardless of whether the original source chain is still enabled.
{% endhint %}
### What Your Depositors See
Once a chain is enabled, depositors connected to that network can pick it from the **Chain** dropdown on your vault's deposit page. For the full depositor walkthrough, see [Cross Chain Deposits](/onyx-user-documentation/investor-interface/cross-chain-subscription.md) in the Investor Interface documentation.
{% hint style="info" %}
Cross-chain deposits incur an additional CCIP messaging fee paid by the depositor as part of the deposit transaction. Bridging from the source chain to the vault chain typically takes 20–30 minutes.
{% 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/administration-app/vault/subscription-management/cross-chain-enablement.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.
