> For the complete documentation index, see [llms.txt](https://docs.mellow.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mellow.finance/restaking-vaults/interoperable-vaults/architecture.md).

# Architecture

#### Overview

This vault type is designed to allow users to delegate stake without direct liquidity transfers across various Layer 2 (source chain) networks to Layer 1 (target chain) with a following steps happening under the hood:

1. A user on an L2 deposits an asset into the vault.
2. The user receives a corresponding receipt token on L2.
3. The deposited liquidity is locked in the vault on L2.
4. An OFT ( LayerZero Omnichain Fungible Token Standard) counterpart is minted on the target chain — Ethereum mainnet, where Mellow restaking vaults are deployed.
5. That OFT is then used as the restaking asset within Symbiotic/EigenLayer vaults to provide shared security. Symbiotic has already whitelisted the OFT to have the same rewards rate as native L1 assets.
6. The user earns rewards in two ways: first, through L2 incentives—some of the vault’s accumulated liquidity is staked directly, and some is used in DeFi strategies on the L2 via the receipt tokens; second, through direct restaking rewards (both tokens and points) from various networks.

If a slashing event occurs, the OFT itself can be slashed. Any non-burned OFT can still be redeemed to unlock the original L2 liquidity.

Visually, the system is divided into:

* **Source Chain (L2):** Users deposit their assets and receive vault shares on L2.
* **Target Chain (L1):** Stake delegation occurs here after cross-chain transfer. The delegated stake is distributed among various yield protocols supported by Mellow MultiVault.

LayerZero's OFT is used for cross-chain interaction with one key modification: deposits into the `OFTAdapter` can only be made via `SourceCore`.

Gas parameters are defined using enforced options in the OFTs.

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


---

# 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.mellow.finance/restaking-vaults/interoperable-vaults/architecture.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.