# Chainlink opens DeFi vault access from more than 80 chains Author: Hatice Ertaş Language: English Published: 2026-10-09T01:13:47+03:00 Updated: 2026-10-09T01:14:15+03:00 ![Ceramic pathways joining at a metal coupling with a Chainlink emblem, symbolising access to one vault from several chains](https://kriptometa.com/uploads/chainlink-ten-defi-kasalarina-den-fazla-agdan-erisim-75a6a4da4ab5_article.webp) ## Key takeaways - The initial implementation focuses on standard, single-asset ERC-4626 vaults. - Supported networks and transferable tokens must be configured for each deployment. - Failed deposits require a separate recovery action, which can involve additional fees. The software connects assets on other networks to a vault while keeping its management on one chain. Aave and Lombard feature among the announced use cases. Chainlink launched CCIP Vault Adapters on October 8, allowing DeFi vaults to accept deposits from more than 80 [blockchains](https://kriptometa.com/en/news/blockchain) supported by CCIP. According to the [company announcement](https://chain.link/blog/introducing-ccip-vault-adapters), providers can keep a vault on one network instead of recreating it on every chain. Its investment strategy and accounting remain on that home chain. A DeFi vault is a [smart contract](https://kriptometa.com/en/glossary/smart-contract) that manages deposited assets under a particular strategy. Depositors receive tokens representing their shares in it. The new software connects assets held on another network to the vault and handles delivery of the resulting shares. ## One vault, deposits from multiple chains The [technical workflow](https://docs.chain.link/solutions/cross-chain-vault-adapter/overview/how-it-works) covers both deposits and redemptions, in which users return shares to withdraw assets. CCIP carries the asset and instructions to the vault’s network. The adapter then executes the vault transaction and delivers the output locally, or sends it back to the originating chain if the required token infrastructure is in place. Support for more than 80 networks does not automatically make every vault available on all of them. The [implementation documentation](https://docs.chain.link/solutions/cross-chain-vault-adapter) requires configured network and vault allowlists, plus support for each transferred token on the relevant CCIP route. The standard implementation handles single-asset ERC-4626 vaults that complete a deposit or redemption within the same vault transaction. Withdrawals with waiting periods and multi-asset vaults require additional development. Chainlink’s official October 8 post includes a 34-second video illustrating how deposits from different networks reach one vault. [Open Chainlink’s video announcement on X](https://x.com/chainlink/status/2108169684721807413) ## How Aave and Lombard use the adapters One example in the announcement is depositing Avalanche-based BTC.b into Lombard’s Bitcoin Onchain Credit Strategy vault on Ethereum. The asset in that route is BTC.b on Avalanche, rather than native BTC on the Bitcoin network. Aave is extending access to its sGHO vault beyond Ethereum, routing larger transactions and liquidity rebalancing through its adapter. The named projects are at different stages. The announcement describes RockawayX as live, Veda as integrating the adapters, and United Stables’ U-denominated vault as an upcoming product. It does not establish a completed launch or disclose actual deposit volumes for every project listed. [Entry and exit costs](https://kriptometa.com/en/defi-beginner-decision-map) include the initial CCIP message fee paid by the user. Returning the output to the originating chain can also incur an adapter fee set by the vault operator. Because the value of a vault share can change while a message is in transit, the request can specify a minimum acceptable output. ## Failed requests do not trigger automatic refunds **Message delivery does not prove a deposit succeeded.** The CCIP explorer can display “Success” even when the vault operation failed. The documentation instructs users to check the adapter’s transaction outcome separately. The [failure and recovery documentation](https://docs.chain.link/solutions/cross-chain-vault-adapter/overview/failures-and-recovery) says failed requests are neither retried nor refunded automatically. Where supported, funds can be returned to the original sender, with the person initiating the refund paying the cross-chain fee. Recovery on the vault’s own network instead depends on a refund address specified in advance. Certain malformed messages can leave funds permanently stuck. The provider operates the vault and adapter. Chainlink says it does not run vaults or recommend particular investment strategies. The announcement offers no guaranteed yield or fixed fee covering every transaction.