Aave makes Chainlink CCIP its default layer for cross-chain activity

One interoperability layer for app and vault activity

Under the change, CCIP becomes the common cross-chain system behind deposits, withdrawals, asset transfers, vault rebalancing, yield optimization, Stable Vault operations, GHO transfers, and governance-related actions. According to Aave, the goal is to place these functions on a single interoperability layer rather than depending on separate systems for different cross-chain tasks.

The expanded setup applies across the Aave App and Stable Vaults. Aave said this means background transfers, token movement, vault management, and governance execution now rely on the same underlying infrastructure.

Stable Vault flows across Ethereum, Base, and Arbitrum

Within the Aave App, Stable Vaults automatically move deposits between Ethereum, Base, and Arbitrum in an effort to improve returns. Aave said CCIP will now handle those transfers in the background, removing the need for users to manually bridge assets before moving funds across supported networks.

Aave Labs previously introduced Stable Vaults as infrastructure that businesses can use to add fixed-rate stablecoin yield to their own applications. According to the protocol, the same vault technology is already used in savings products available through the Aave App.

GHO transfers and token model across networks

Aave said GHO and Savings GHO also use CCIP through Chainlink’s Cross-Chain Token standard. According to the protocol, GHO is available on eight blockchain networks, with CCIP providing the transfer infrastructure between those supported chains.

The protocol described two different mechanisms for moving GHO across networks. Transfers from Ethereum to supported layer-2 networks use a lock-and-mint model. Transfers between other supported chains use a burn-and-mint process that Aave said is designed to preserve GHO’s total supply while keeping the token fungible across networks.

Governance and security design

Cross-chain governance will continue to run through the Aave Delivery Infrastructure, or a.DI. Aave said proposals approved on Ethereum can be executed on other blockchain networks where the lending protocol is deployed, allowing governance instructions and related asset transfers to use the same communication layer.

The protocol also framed the latest decision as an extension of a longer relationship with Chainlink. Aave said that relationship began in January 2020, when it adopted Chainlink Data Feeds as its oracle infrastructure. CCIP now operates alongside those services through Chainlink’s decentralized oracle network.

According to Aave, security remains a core part of the design. The protocol said each CCIP bridge lane it uses is secured by at least 16 independent node operators across different organizations, geographic regions, and infrastructure providers. It added that the system includes rate limits intended to restrict how much value can move between networks during abnormal conditions.

The update does not introduce a new standalone product, but it consolidates more of Aave’s cross-chain operations under one system. In practice, that means the infrastructure already used for GHO transfers and governance messaging is now also responsible for a broader set of actions across the Aave ecosystem, including app-level transfers and Stable Vault management.