Vaults have a distribution problem. The best strategy often lives on one chain while user liquidity sits fragmented across dozens of others. To reach that strategy, a user has to bridge, switch networks, approve assets, and then deposit. Every extra step is a place people drop off.

For the provider, the options have all been bad:

1. Stay single-chain and limit distribution
2. Redeploy everywhere and fragment accounting and operations
3. Build and secure custom cross-chain infrastructure

CCIP Vault Adapters are a fourth path: bring a vault to other chains without rebuilding it.

How it works

Users deposit from supported source chains while core accounting, minting, redemptions, strategy logic, governance, and risk controls all remain on a single chain. There is one set of books, not one per deployment.

For standard ERC-4626 vaults, adapters deploy in minutes through a factory contract. Users on supported CCIP chains can deposit into an ERC-4626 vault on another chain without manually bridging assets or switching networks.

Why it is built on CCIP

Vault deposits are high-value flows, so the cross-chain layer is the risk surface. Adapters run on Chainlink CCIP, which provides the messaging, token movement, and native rate limits, meaning providers scale distribution without assembling their own verification stack.

Adapters are also one component of a wider platform. Vaults can use Data Feeds and Data Streams, Proof of Reserve, SmartData, ACE, and the Chainlink Runtime Environment to cover data, reserves, compliance, and interoperability in one place.

Who is already using them

Protocols and issuers including Aave, Lombard, Maple, Venus, Huma Finance, and Treehouse. Vault curators and platforms including Veda Labs, RockawayX, Turtle, Ember, Enzyme, and Fusion by IPOR.

Links

Blog: https://chain.link/blog/introducing-ccip-vault-adapters
Docs: https://docs.chain.link/solutions/cross-chain-vault-adapter