> 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/investor-interface/cross-chain-subscription.md).

# Cross Chain Subscription

## Cross-Chain Deposits

You can deposit into an Onyx vault from a blockchain different from the one the vault lives on. The transfer is secured by [Chainlink CCIP](https://chain.link/cross-chain), Chainlink's cross-chain interoperability protocol.

{% hint style="info" %}
The ***Source Chain*** is the chain where you hold the deposit asset and initiate the transaction. The ***Vault Chain*** is the chain where the vault lives and where your deposit ultimately settles and your shares are minted.
{% endhint %}

### Making a Cross-Chain Deposit

The cross-chain flow follows the same shape as a standard deposit — see [Deposits](/onyx-user-documentation/enzyme-vault/subscription/deposits.md) for the general lifecycle. The sections below cover only what is different when depositing from another chain.

#### Selecting a Source Chain

On the vault's deposit page, open the **Chain** dropdown next to the amount field. The dropdown lists every chain the vault admin has enabled as a source. Pick the chain you currently hold the deposit asset on.

If your wallet is connected to a different network than the chain you select, you will be prompted to switch networks before continuing. The form inputs remain disabled until your wallet is on the correct chain.

<figure><img src="/files/W4yuwoP1mAEkVdh0nEL0" alt=""><figcaption></figcaption></figure>

#### Approving and Submitting

Cross-chain deposits use the same two-step pattern as native deposits: first **Approve {Asset}**, then **Execute Deposit**. Both transactions are signed on the source chain. Tick the terms checkbox to enable the buttons.

#### Bridging Time

Once you submit **Execute Deposit**, the transaction is confirmed on the source chain within seconds. The CCIP message then travels to the vault chain, where your deposit is processed and your shares are minted. Delivery typically takes **20–30 minutes**.

After submission, an alert on the deposit page links to the **CCIP Explorer** (`https://ccip.chain.link/tx/{your-tx-hash}`) where you can track the bridging progress in real time.

{% hint style="info" %}
A cross-chain deposit pays an additional CCIP messaging fee on top of standard network gas. The fee is included in the **Execute Deposit** transaction — you do not need to send a separate payment.
{% endhint %}

### Redeeming Shares from a Cross-Chain Deposit

Vault shares always live on the **vault's chain** — they are never bridged back to the source chain you deposited from. Despite that, you do not need to switch your wallet to the vault chain to redeem them. The redeem page lets you initiate redemption directly from the source chain, and CCIP relays the request across for you. See [Redemptions](/onyx-user-documentation/enzyme-vault/subscription/redemptions.md) for the general redemption flow.

{% hint style="info" %}
Shares from a cross-chain deposit are held in a wallet on the vault chain that you control through your source-chain address. From your perspective, you simply stay on the source chain throughout deposit, redemption, and any cancellation.
{% endhint %}

#### Selecting Where to Redeem From

On the vault's redeem page, the **Chain** dropdown lists every chain from which you currently have redeemable shares, including any held from past cross-chain deposits. Each option shows the chain and the available share balance. Pick the entry that matches the source chain of your original deposit.

<figure><img src="/files/HurMAe3mzMbJrAuryJwg" alt=""><figcaption></figcaption></figure>

#### Submitting a Cross-Chain Redemption

Connect your wallet to the source chain you selected. The submission signs a CCIP message on that chain, which travels to the vault chain and queues the redemption request there — you do not need to interact with the vault chain yourself. An additional CCIP messaging fee applies, similar to a cross-chain deposit.

{% hint style="info" %}
Cross-chain redemption goes through your vault's standard redemption queue once the CCIP message is delivered. Final settlement timing depends on the vault's redemption policy in addition to the 20–30 minute CCIP bridging window.
{% endhint %}

### Cancelling a Cross-Chain Deposit

Cross-chain deposits can be cancelled from the **Pending Deposit Requests** table once their cancellation window has elapsed. Because the original deposit travelled across chains, the cancellation must travel back the same way — this requires a second CCIP message, which has its own fee.

#### Approving the Return Fee

Connect your wallet to the **source chain** of the original deposit. The modal displays the wrapped native token required to pay the CCIP return-message fee (for example, **WETH** on Ethereum), the exact amount needed, and your current balance. Click **Approve** to authorise the fee token.

<figure><img src="/files/xQ7YMXwSD9xGZS2HmKal" alt=""><figcaption></figcaption></figure>

#### Submitting the Cancellation

After the approval confirms, the modal advances to step two. Click **Cancel Deposit Request** to sign the cancellation. This sends a CCIP message from the source chain to the vault chain instructing it to return your deposit.

#### Waiting for the Return

CCIP relays the cancellation message and then ships the returned funds back to your wallet on the source chain. The full round trip typically takes a few minutes to around 30 minutes. A toast notification confirms submission and links to the CCIP Explorer.

{% hint style="info" %}
Do not submit a second cancellation for the same deposit while the first is in flight. Wait until the return is delivered before taking further action.
{% 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 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://docs.enzyme.finance/onyx-user-documentation/investor-interface/cross-chain-subscription.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.