What Is OVault? LayerZero's Vault Standard
OVault is LayerZero's omnichain vault standard — a pattern that lets a single ERC-4626 vault on one "hub" chain serve users on any other LayerZero-connected chain, without fragmenting liquidity or deploying separate vault instances everywhere. Launched in 2024 and now powering vaults from Ethena, Hyperdrive, and Resolv, OVault has become the default way to build yield-bearing or structured vault products that behave natively across multiple chains. This guide explains the architecture, the two token types that make it work, the risk controls, and how stablecoin orchestration layers like Eco Routes integrate.
You will understand how the VaultComposerSync contract works, why Share OFTs and Asset OFTs are different, what the two-phase operation flow protects against, and where routing fits when stablecoin capital needs to flow into or out of an OVault-powered vault.
OVault at a glance
OVault is a hub-and-spoke composer architecture built on top of LayerZero's LayerZero messaging protocol and its Omnichain Fungible Token (OFT) standard. The vault itself lives on a single hub chain. Users on any other LayerZero-connected chain can deposit assets and receive shares as if the vault were local — the OVault components handle the cross-chain accounting.
The key primitives:
Hub vault — a standard ERC-4626 tokenized vault contract deployed on one chain.
VaultComposerSync — the composer contract that translates cross-chain deposit and withdraw intents into vault operations.
Asset OFT — an omnichain representation of the vault's underlying asset (for example, USDe).
Share OFT — an omnichain representation of the vault's share token (for example, sUSDe).
Because LayerZero is a partner rail for Eco Routes, OVault integrations sit naturally inside the broader cross-chain stablecoin stack. Eco Routes abstracts the chain-picking and bridging decisions, and can move stablecoins into OVault-enabled products on all 15 supported chains where the vault's OFTs are deployed. Teams building programmable yield products often pair OVault with the programmable stablecoin protocols stack for deposit automation.
The problem OVault solves
Before OVault, a team launching a yield vault had three bad options for multichain support.
Option one: deploy separate vault instances on every chain, each with its own liquidity, strategy, and price. This fragments TVL, makes yield inconsistent, and creates operational overhead. Option two: pick one chain and force users to bridge manually before interacting. This bleeds user retention. Option three: use a custom cross-chain solution with bespoke messaging and risk — expensive to build and audit.
OVault packages the third option into a standard. The team builds one vault on the hub chain, defines the Share OFT and Asset OFT, deploys the VaultComposerSync, and the vault is effectively available everywhere LayerZero is live. No duplicated liquidity, no per-chain strategy management, and no bespoke cross-chain code.
This matters for the broader onchain capital market. The Bank for International Settlements has noted that tokenized asset fragmentation is one of the main frictions in crypto capital markets. A standard like OVault reduces that fragmentation for yield products specifically.
Hub-and-spoke architecture
The hub-and-spoke layout is what makes OVault scale. Here is the flow for a cross-chain deposit.
User on Chain B (a spoke) holds Asset OFT (the omnichain underlying — for example, omnichain USDe).
User calls the local VaultComposerSync on Chain B with a deposit intent: "deposit X Asset OFT, receive Y Share OFT."
VaultComposerSync sends a LayerZero message to the hub chain (Chain A), burning the Asset OFT on Chain B and minting it on Chain A.
On the hub, VaultComposerSync receives the asset and calls the ERC-4626 vault's deposit function on behalf of the user.
The vault mints shares; the composer wraps them as Share OFT and delivers them back to the user on Chain B via a return LayerZero message.
Withdrawals run the same loop in reverse. Every step is atomic inside each chain, and the two-phase operation (more on this below) protects the user if the cross-chain leg fails.
Share OFTs vs Asset OFTs
OVault defines two OFT types with different behaviors. Understanding the split is the single most important thing for integrators.
Asset OFT
The Asset OFT is the omnichain form of the vault's underlying asset. If the hub vault takes USDe as deposits, the Asset OFT is omnichain USDe. Users can hold it anywhere, send it across chains via LayerZero, and deposit it into the OVault composer on any supported chain. Asset OFTs behave like any standard OFT — fungible across chains with burn-and-mint bridging.
Share OFT
The Share OFT is the omnichain form of the vault's share token. If the vault mints sUSDe shares, the Share OFT is omnichain sUSDe. Users hold it, trade it, or use it as collateral on any chain. The value of Share OFT tracks the vault's share price, which updates via the hub's ERC-4626 logic and is surfaced to spokes through cross-chain read calls.
The split keeps accounting clean: deposits move Asset OFTs toward the hub, withdrawals move them away. Shares track separately. Each OFT can have its own deployment footprint, so a team might launch Share OFT on fewer chains than Asset OFT in the early days.
Launch partners powering OVault in 2026
Three major protocols have built production OVault deployments, with combined vault TVL over $7 billion.
Ethena sUSDe
Ethena's USDe synthetic dollar and its yield-bearing staked variant sUSDe are the flagship OVault deployment. sUSDe TVL crossed $5.6 billion in early 2026, with omnichain availability across Ethereum, Arbitrum, Base, Optimism, and Solana. Ethena's integration showed the market what a production OVault looks like — deposits and withdrawals behave the same on every chain, and Share OFT composability unlocked integrations with DeFi money markets and structured products.
Hyperdrive (HyperEVM)
Hyperdrive is the native money market on the Hyperliquid L1. Its OVault deployment lets users on other chains supply collateral into Hyperdrive markets without first bridging to HyperEVM manually. The flow is standard OVault: deposit Asset OFT on the origin chain, receive Share OFT that represents the Hyperdrive position. Hyperdrive's growth has been driven in part by this frictionless multichain access.
Resolv wstUSR
Resolv's wstUSR — a wrapped, rebasing-free version of its USR staking token — uses OVault for cross-chain supply. Resolv was one of the first protocols to launch Share OFT liquidity natively on multiple chains, rather than relying on third-party bridge wrappers.
Risk management: two-phase operations and slippage protection
Cross-chain vault operations are inherently trickier than local ones. OVault's risk model has two main defenses.
Two-phase operations
Every cross-chain deposit or withdraw is a two-phase operation. Phase one executes on the origin chain (burning the Asset OFT or locking shares). Phase two executes on the hub chain (minting in the vault or pulling shares). If phase two fails — due to a revert, a slippage breach, or a dust edge — the composer refunds the user on the origin chain. Funds are never stuck in limbo between the two legs.
Slippage protection
When an OVault deposit lands on the hub, the vault's share price may have moved since the user signed. OVault composers accept user-supplied minimum-shares-out parameters. If the received shares would fall below the user's threshold, the composer reverts and refunds. The same applies to withdrawals — users set minimum-assets-out.
LayerZero DVN security
All OVault messages travel over LayerZero, which uses decentralized verifier networks (DVNs) that the vault deployer configures. Teams can pick multiple DVNs, set required confirmations, and add thresholded verification. The LayerZero publications library covers DVN configuration and the security model in depth, and teams often cross-reference L2Beat bridge research when comparing DVN sets against other cross-chain verification designs.
Where OVault fits in the rail-layer-app model
Eco's 3-tier framing makes it easier to place OVault inside the broader cross-chain stack.
Rail tier — LayerZero (along with CCTP, Hyperlane, and Wormhole) provides the underlying cross-chain messaging and token bridging primitives. OVault is built on the LayerZero rail specifically, using OFTs as its token model.
Layer tier — orchestrators like Eco Routes sit above the rails and pick between them per transaction based on cost, speed, and finality. OVault does not replace this layer; it co-exists with it.
App tier — the end-user vault (Ethena's sUSDe, Hyperdrive's markets, Resolv's wstUSR) sits on top of both. Users experience a single product; behind the scenes, OVault handles vault accounting and a routing layer handles stablecoin movement.
The separation is useful for integrators. If you are shipping a vault, OVault solves the "expose this vault to users on other chains" problem. If you are shipping an app that routes capital into vaults, a layer like Eco Routes solves the "move stablecoins across chains" problem. The two are orthogonal and composable. The intent settlement layers overview covers the settlement-layer decision in more detail, and the cross-chain messaging protocols breakdown compares the underlying rails.
OVault vs alternative cross-chain vault patterns
OVault is one of several approaches to multichain vaults. The main alternatives:
Chain-native vaults with bridge wrappers — a single-chain vault with third-party bridge wrappers on other chains. Simpler but fragments liquidity across wrappers and loses composability.
Intent-based vault adapters — users sign intents to a solver that executes the deposit cross-chain. Flexible but requires solver infrastructure and adds a principal-agent layer.
CCIP-based vaults — similar architecture to OVault but built on Chainlink CCIP messaging. Trades LayerZero's DVN model for Chainlink's decentralized oracle network.
Each pattern has trade-offs. OVault's advantage is standardization — a vault team that knows ERC-4626 can adopt OVault with a clearly documented composer pattern. The stablecoin sweep automation tools piece covers where intent-based patterns complement vault flows.
How Eco Routes integrates with OVault
OVault handles the vault's own cross-chain accounting once the Asset OFT is on the user's chain. But getting stablecoins into Asset OFT form is a separate problem — one Eco Routes solves natively.
Take a concrete flow: a user holds USDC on Base and wants to deposit into Ethena's sUSDe vault (hub on Ethereum, Share OFT available on Arbitrum). The path is:
Eco Routes moves USDC from Base to the user's preferred OVault-supported chain, picking between Circle CCTP, LayerZero, Hyperlane, or Wormhole based on cost and speed.
A swap or mint converts USDC into USDe (Ethena's underlying), producing the Asset OFT on the chosen chain.
The user (or the application) calls the OVault composer to deposit USDe and receive sUSDe Share OFT.
Eco Routes supports USDC, USDT, USDC.e, oUSDT, USDT0, USDbC, and USDG across all 15 supported chains (Ethereum, Optimism, Base, Arbitrum, HyperEVM, Plasma, Polygon, Ronin, Unichain, Ink, Celo, Solana, Sonic, BSC, Worldchain). Applications integrate through the Routes CLI or Routes API, and routing decisions stay abstract from the vault integration logic.
The broader pattern — orchestrator on top of rails — is a deliberate separation. LayerZero, CCTP, Hyperlane, and Wormhole are the rails. Eco Routes is the orchestration layer that picks between them per transaction. OVault is a standard built on LayerZero's rail. Teams integrating OVault typically benefit from also integrating a routing layer so their users can deposit from any chain holding any supported stablecoin. The cross-chain intent protocols overview explains this orchestration pattern in depth.
When to use OVault
Teams considering an OVault deployment should check a few conditions.
You have a clear ERC-4626 vault on a single hub chain and want users on other chains to access it without deploying duplicate vaults.
Your underlying asset can be wrapped as an Asset OFT (most stablecoins and yield tokens qualify).
You are comfortable with LayerZero's DVN security model and can configure appropriate verifier sets.
Your user base spans multiple chains — if the vast majority of users are on one chain, OVault adds complexity without benefit.
For vaults focused on stablecoin yield — the largest current use case — OVault plus a routing layer like Eco Routes is the cleanest multichain deployment pattern available today. Teams comparing options often start with the cross-chain liquidity protocols overview and the stablecoin rebalancing tools breakdown before settling on a deployment pattern.
Frequently asked questions
Is OVault the same as LayerZero OFT?
Not exactly. OFT is the base omnichain fungible token standard. OVault is a specific pattern that uses OFTs (Asset OFT and Share OFT) together with the VaultComposerSync contract to expose a single ERC-4626 vault across chains. OVault is built on top of OFT, not a replacement for it.
What happens if a cross-chain OVault deposit fails?
OVault uses two-phase operations with refund logic. If the hub-chain leg reverts (for example, because slippage breaches the user's minimum-shares threshold), the composer refunds the Asset OFT on the origin chain. Funds are not stuck between chains — they return to the user after a small cross-chain round-trip.
Which vaults use OVault today?
Ethena's sUSDe (over $5.6B TVL) is the flagship deployment. Hyperdrive's HyperEVM money market and Resolv's wstUSR are the other major production OVault integrations. More vault teams are onboarding throughout 2026, especially stablecoin-yield and tokenized Treasury products.
Can Eco Routes deposit USDC directly into an OVault-powered vault?
Eco Routes handles the stablecoin routing leg: moving USDC, USDT, or other supported stablecoins to the chain where the user wants to deposit. From there, the OVault composer handles the cross-chain vault accounting. Applications typically chain the two calls to deliver a one-step UX.
Is OVault audited?
Yes. LayerZero's core contracts and the OVault reference implementation have been audited by multiple firms. Each deploying protocol (Ethena, Hyperdrive, Resolv) also audits its own composer configuration and vault strategy. Teams considering OVault should review both the protocol audit and their own integration path.
Bottom line
OVault is the default way to ship a multichain ERC-4626 vault in 2026. Its hub-and-spoke composer architecture, Asset and Share OFT split, and two-phase risk model solve the fragmentation and UX problems that plagued earlier multichain vault attempts. Ethena, Hyperdrive, and Resolv have proven the pattern at scale. For stablecoin capital flowing into OVault-powered products, orchestration layers like Eco Routes complement the standard — routing stablecoins across all 15 supported chains and feeding the Asset OFT side of any OVault deployment. Vault standard from LayerZero, routing from Eco Routes, rails underneath. Composable by design.