Chainlink's CCIP Vault Adapters Go Live for 80+ Blockchains

Chainlink said its CCIP Vault Adapters are live, letting a DeFi vault on a single network accept deposits from more than 80 supported blockchains with a single click. The adapters run on CCIP, Chainlink's Cross-Chain Interoperability Protocol, and use its Programmable Token Transfer capability so a depositor on a source chain moves funds straight into a vault on the destination chain instead of bridging manually and depositing afterwards. Chainlink published the details in its launch post.

The Problem the Adapters Target

A vault is deployed on one chain while its depositors hold assets on many. Under the standard flow an issuer either deploys a copy of the vault per chain or asks users to bridge, switch networks and deposit in separate transactions.

Chainlink's version keeps vault logic, accounting, governance and risk parameters on a single home chain, with adapters pulling deposits in from supported source chains. That removes the duplicate deployments an issuer would otherwise maintain, and it keeps vault TVL in one place rather than spread across forks of the same strategy.

Which Protocols Are On Board

Chainlink named Aave, Lombard, United Stables, Veda and Venus among the adopters, with Re, World Liberty Financial, Accountable, Turtle, Saturn, Huma Finance and RockawayX also listed. Several of the named use cases are specific.

Lombard routes BTC deposits into its Bitcoin Onchain Credit Strategy, so a Bitcoin holder on Avalanche (BTC.b) can deposit into Lombard's Ethereum vault without bridging first. Aave is extending its sGHO vault beyond Ethereum, with instant GHO/sGHO swaps on supported networks and larger transactions plus liquidity rebalancing routed through its CCIP Vault Adapter. Veda, which Chainlink describes as handling more than $32 billion in volume across 200+ vaults, is integrating to widen access to the vaults it powers. RockawayX is already live, Chainlink said.

United Stables is building its upcoming U-denominated vault around the adapters, with a cross-chain deposit path designed in from day one. Distribution has been the constraint on vault growth as much as yield, and Plume's tokenized vault backed by a Fidelity bond ETF is a recent example of a product launched around access to an asset that already exists.

Integration for ERC-4626 Vaults

Standard ERC-4626 vaults can integrate the adapters in minutes through a factory contract, with no custom cross-chain code required, per Chainlink. The adapters ship with separate admin, fee setter and fee collector roles, and with failed message handling that gives stuck funds a path back to the owner if a deposit reverts on the destination chain.

A vault's receipt token can also be made a Cross-Chain Token, giving depositors the option to bridge their vault shares to another chain. Providers can configure adapters to accept any asset from any supported chain, including assets using the CCT standard that do not run on CCIP natively.

Chainlink said the initial focus is ERC-4626 cross-chain deposits and redemptions. Asynchronous vault interactions, cooldowns, multi-asset and permissioned vault adapters are still to come. Vault workflows can also call other Chainlink services, including Data Feeds, Data Streams, Proof of Reserve, SmartData, the Automated Compliance Engine and the Chainlink Runtime Environment.

What Chainlink Has Not Published

The chain list behind the 80+ figure is not in the post, and two Chainlink documentation pages for the product returned 404 when checked, so which networks can act as source chains or destination chains is unverified. Chainlink also does not say which named adopters have live adapters and which have announced intent only. The vault TVL the adapters already reach is Chainlink's own claim, and no third-party figure for it appeared in the material reviewed.

Chainlink's post carries a disclaimer that it does not deploy, control or operate any vault or vault adapter, and does not endorse any particular vault or strategy. The roadmap items, asynchronous vault interactions and permissioned adapters among them, are the next observable checkpoints on whether the single-click deposit flow reaches past the ERC-4626 standard.