Chainlink on October 8 introduced a tool for vaults that want deposits from other chains without moving the strategy.
The thread calls the product CCIP Vault Adapters and describes it as one-click cross-chain deposit infrastructure. Users can deposit from chains; Chainlink says more than 80. Strategy and accounting stay on one chain. The message is carried by CCIP, the cross-chain protocol Chainlink, upgraded on September 28. Getting started is documented at the vault-adapter page.
Why Chainlink says vaults are stuck on one chain
The thread’s framing is a distribution problem. A strategy may live on one network while the deposits sit on others. Today, Chainlink says, a user often has to bridge, switch networks, approve the asset, and then deposit. Each step is a place to stop.
Providers, in the same thread, have three poor options: stay on one chain and cap the audience, redeploy the vault everywhere and split accounting, or build and secure their own bridge. The adapter is the fourth path Chainlink is selling. A provider keeps one set of books. Users on a supported source chain send a deposit without manually bridging or switching networks.
That is the claim in the thread. It is not a count of deposits already sent through the new adapter.
What stays on the hub, and what the user sends
Chainlink’s docs say the adapter is a contract on the hub chain. It receives tokens and instructions through a CCIP message and calls the vault. Accounting, including share minting, burning, and yield, stays on that hub. No copy of the vault or its share price runs on the source chain.
For a deposit, the user approves the CCIP router and sends one message: the asset, the vault name, the beneficiary, a minimum output, a delivery option, and a local refund address. The payload is 128 bytes. Shares can be delivered on the hub or back on the source chain. A redemption reverses the flow. The user does not deploy a contract.
For a standard ERC-4626 vault, Chainlink says the adapter can be deployed in minutes through a factory, CrossChainERC4626AdapterFactory, in one transaction on the hub. That call sets the accepted source chains, allowlists the vault, sets deposit and redeem switches and fees, and assigns admin, fee-setter and fee-collector roles. The factory then renounces its roles. One adapter can serve more than one vault on the same chain.
CCIP supplies the messaging, the token movement, and the native rate limits. The thread says a provider does not have to assemble its own verification stack. The docs require a CCIP lane between the source and the hub. Solana is named as a source alongside EVM chains. The lane list lives in Chainlink’s CCIP directory, not in the thread.
Who Chainlink says is already using it
The thread’s adopter post splits the names into two groups.
- Protocols and issuers: Aave, Lombard, Usual Tech Stables, Maple, World Liberty Financial, Venus, Re, Tenbin Labs, Huma, Stable, Saturn Credit, Tori, and Treehouse.
- Vault curators and platforms: Veda, RockawayX, Accountable, K3 Capital, Turtle, Ember, Fusion by IPOR, Enzyme, Mezzanine, and R25.
“Already adopted” is Chainlink’s label. The thread does not give volumes, live vault addresses, or a date each name switched on. Aave is not a new CCIP user. The Crypto Times reported in July that Aave Labs had picked CCIP for cross-chain deposits and transfers in its upcoming app. This thread puts Aave on the vault-adapter list. It does not say the July app has shipped.
What the docs exclude
The stock adapter is narrower than the thread’s “any chain” line. The docs say the vault must be a synchronous, single-asset ERC-4626, with a standard ERC-20 asset and share token. Fee-on-transfer and rebasing tokens are out. Asynchronous vaults, multi-asset vaults, and non-ERC-4626 targets need a fork. The hub vault must be Shanghai-compatible, meaning it supports the PUSH0 opcode.
Processing failures are held, not reverted. If the vault call fails, the adapter keeps the tokens and records a failed message. Delivery on CCIP is not paused. Recovery is manual, through refundFailedMessage or recoverFailedMessageLocally. A refund goes to the original sender, not the beneficiary, and local recovery needs a refund address set in advance.
The docs also say nothing checks the payload before the tokens reach the hub, and a malformed payload can strand tokens permanently. The adapter needs a native-gas balance to pay the return leg. If that balance is short, the message fails.
The thread points to the rest of the Chainlink stack—Data Feeds, Data Streams, Proof of Reserve, SmartData, the Automated Compliance Engine, and CRE—as tools a vault can add. Those are separate products. They are not switched on by deploying the adapter.
The Crypto Times reported CCIP 2.0 on September 28, including issuer-run verifiers and compliance controls, and Chainlink’s figures of more than $84 billion in cross-chain value secured through CCIP and more than $15 billion migrated onto it in four months. The vault adapter is a later product on that rail. It is not a second version of CCIP.
LINK did not mark the post
OKX’s daily row for October 8 shows LINK opening at $13.428, ranging from $13.260 to $13.522, and last marked at $13.368, on about $4.48 million of venue volume. The prior close was $13.428, so the session was flat to slightly down on that table, inside a week that had already traded from about $13.20 to $14.65. The post went out at 12:16 UTC. The day’s high on that row, $13.522, is 0.7% above the open. There is no discrete jump in the session range to attach to the thread.
A separate quote later on October 8 had LINK near $13.03, down about 2.8% over 24 hours, with a market cap near $9.8 billion. The all-time high on the OKX history page is $52.99. The adapter announcement did not reprice the token on the figures available the same day.
Also Read: Chainlink (LINK) Price Prediction 2026, 2027-2030: Can It Hit a New All-Time High?
