Aave has selected Chainlink’s Cross Chain Interoperability Protocol as the default infrastructure for cross chain activity across its ecosystem, expanding the integration to cover the Aave App and Stable Vaults.
CCIP already supports transfers of Aave’s $GHO stablecoin and cross chain governance through the Aave Delivery Infrastructure, known as a.DI. The system will now also handle the Aave App’s cross chain operations, including deposits, withdrawals, vault rebalancing, yield optimization, and asset transfers.
The Aave App uses Stable Vaults to move deposits and optimize yield across Ethereum, Base, and Arbitrum. CCIP will process those actions in the background, removing the need for users to manually bridge assets before depositing them into another network.
Aave Labs introduced Stable Vaults as an infrastructure product that allows businesses to add fixed rate stablecoin yield to their own applications. The same vault technology already powers savings products inside the Aave App.
$GHO and Savings $GHO also use CCIP through Chainlink’s Cross Chain Token standard. $GHO is currently available across eight networks, with CCIP providing a shared system for moving the stablecoin between supported chains.
The system uses a lock and mint model when moving $GHO from Ethereum to supported layer 2 networks. For transfers between other networks, CCIP can use a burn and mint structure designed to preserve $GHO’s total supply and fungibility.
Aave governance uses the same infrastructure through a.DI, which allows proposals approved on Ethereum to be executed across other networks where the protocol operates.
The expanded integration gives Aave one system for handling token transfers and the instructions attached to them. This allows actions such as deposits, withdrawals, vault reallocations, and governance executions to move data and assets together instead of relying on separate infrastructure for each operation.
Aave said the decision builds on its existing relationship with Chainlink. Chainlink Data Feeds have served as the protocol’s oracle infrastructure since January 2020, while CCIP operates through the same broader decentralized oracle network.
Each CCIP bridge lane used by Aave is supported by at least 16 independent node operators distributed across different organizations, locations, and infrastructure providers. The system also applies rate limits that restrict the amount of value that can move between networks during abnormal conditions.
