Thursday, October 8 · Indianapolis

Dashboard

Markets

Chainlink CCIP Vault Adapters take deposits from 80 chains

The books stay on one chain. Aave, Lombard, and Maple are on the card. The strategy does not move.

BPP

Oct 8, 2026 · 8:27 a.m. ET · 3 min read

Chainlink CCIP Vault Adapters take deposits from 80 chains

Chainlink introduced CCIP Vault Adapters on October 8, 2026. A vault can take deposits from more than 80 chains while the strategy and the accounting stay on one chain. Chainlink said Aave, Lombard, and Maple are already on it. The post is here:

The line people will send is the one Chainlink put under the announcement. Vaults have a distribution problem. The best strategy may live on one chain while the money that could use it sits on others. A depositor often has to bridge, switch networks, approve the asset, and only then deposit. A vault that wants those users has had three bad choices: stay on one chain and miss the money, copy the vault onto every chain and split the books, or build and secure its own bridge. The adapter is the fourth path. The user stays where the money already is. The vault does not pack up and move.

Chainlink's own docs describe the mechanism in one sentence. A CCIP adapter lets users on other chains deposit into and redeem from an existing ERC-4626 vault, while the accounting stays on the hub chain. Every deposit and every redemption still executes against that vault. The user approves the CCIP router and sends one message. The message carries the asset and a short payload. The adapter deposits it, then the shares can stay on the hub chain or travel back to the chain the user started on. For a standard ERC-4626 vault, Chainlink says the adapter can be deployed in minutes through a factory contract. The docs add that Solana can be a source chain. The written guide covers the EVM chains.

The security claim is also theirs, and it is specific. The adapters sit on CCIP, so the cross-chain piece is Chainlink messaging, Chainlink token movement, and CCIP's native rate limits. The vault provider does not assemble a separate verification stack to accept a deposit from somewhere else. CCIP 2.0, which Chainlink turned on September 28, is the protocol under this. October 8 is the vault-shaped use of it. It is not a second network.

The adopter card is long, and one name on it has already drawn a line. Chainlink lists Aave, Lombard, Maple, World Liberty Financial, and Venus among the protocols and issuers, and Veda, RockawayX, Enzyme, and Fusion by IPOR among the curators and platforms. The rest of the names are on the post. Fusion answered the same morning. It called itself an early integrator and said the adapters will be available to its operators, on an opt-in basis, later this year. Adopted, on Chainlink's card, is not the same sentence as live for every Fusion operator today. The examples Fusion gave are the ones a reader can picture: a Base vault holding a lending position on Ethereum while the net asset value is still calculated on Base, a wallet on Arbitrum offering a Fusion vault that lives on Base, or a fund whose custody is Ethereum-only holding a strategy that runs on Base.

What comes next is a factory deployment, not a new chain. An operator with an ERC-4626 vault starts at the docs Chainlink linked, deploys the adapter, and leaves the strategy where it already is. The depositor sends one message instead of a bridge and a network switch. The books stay in one place. That is the sentence worth forwarding.

Morning note

Before the cash open.

One note. It goes to the desk, not just this browser.