- LlamaRisk assessed cross‑chain options and found Chainlink CCIP to be the most secure.
- Aave’s been using Chainlink oracles since 2020 and CCIP for GHO transfers and governance.
- According to Aave, security was the deciding factor when choosing CCIP.
Aave Labs announced that it has adopted Chainlink’s Cross-Chain Interoperability Protocol (CCIP) as the main cross‑chain infrastructure behind its new mobile app and wider cross‑chain ecosystem.
The integration comes after an updated LlamaRisk assessment that compared cross‑chain options and found Chainlink CCIP to be the most secure. It concluded that CCIP doesn’t add any extra trust requirements beyond what Aave already relies on.
Aave has been using Chainlink oracles since 2020 and CCIP for GHO transfers and governance. Now it’s building on that foundation to make multichain interactions smoother for users.
Beyond Data Feeds, Aave now depends on Chainlink for cross‑chain messaging, governance, GHO transfers, and app infrastructure.
What is Chainlink CCIP?
CCIP is Chainlink’s system for moving digital assets, messages, instructions, and smart contract data securely across different blockchains. Instead of building different bridges for each chain (such as Ethereum, Base, Arbitrum, Avalanche, and others), developers can just integrate CCIP once and use one standardized communication layer. CCIP is basically a universal transport system that connects them all.
According to Aave, security was the deciding factor when it chose CCIP.
It cited several other reasons for going with CCIP, including that each bridge lane is backed by at least 16 independent node operators spread across different organizations and regions. Additionally, native rate limits kick in during abnormal conditions, and everything (like messages and token transfers) runs through a unified interface.
As such, by standardizing on CCIP, Aave can grow to more chains without compromising security or user experience.
Aave Tightening Its Risk Framework
The company stated that every dependency used by the protocol must meet strict criteria outlined in the Aave Technical Asset Listing Framework and the updated LlamaRisk’s Aave Risk Framework.
In June, LlamaRisk proposed a protocol-wide risk framework for all of Aave’s V3, V4, and Horizon deployments. Assets that don’t meet the new requirements could be dropped, which is a sign that Aave is getting more serious about risk management.
Interestingly, earlier this month, Aave saw activity picking back up, with the biggest single‑day surge in new users in nearly five years.
Related: Aave Labs Unveils Asset Listing Framework for Token Listings
Disclaimer: The information presented in this article is for informational and educational purposes only. The article does not constitute financial advice or advice of any kind. Coin Edition is not responsible for any losses incurred as a result of the utilization of content, products, or services mentioned. Readers are advised to exercise caution before taking any action related to the company.
