Aave DAO considered an Aave v3 deployment on X Layer

What happened

An official Aave DAO ARFC proposed deploying a new Aave v3 instance on X Layer and supplied an indicative initial asset set and risk configuration.

What changed

The proposal placed a chain-specific Aave deployment, its collateral set, cross-chain dependencies, oracles, caps, and liquidation parameters into formal governance review.

What did not change

The ARFC did not itself deploy or activate contracts. Its stated parameters were indicative, so it did not establish final live assets, caps, LTVs, oracle routes, governance messaging, or advisor approval for the new instance.

Confirmed

• The proposal targeted an Aave v3 instance on X Layer.
• The indicative asset set included USDT0, USDG, GHO, xBTC, wOKB, xETH, xSOL, xBETH, and xOKSOL.
• The proposal included indicative collateral, cap, interest-rate, and E-Mode parameters.
• The proposal stated that parameters required further risk-provider feedback.

Still open

• The vote outcome and any subsequent AIP or execution were not established by this candidate.
• Final parameters and the deployed contract-address registry were not confirmed.
• The security and operational properties of X Layer, cross-chain governance, bridges, and oracle dependencies required separate diligence.
• No evidence established that the X Layer instance inherited Ketju's approval for other Aave v3 markets.

What it means for an advisor

• Track the proposal through on-chain execution and require a chain-specific memo before considering exposure.
• Do not treat the protocol-level Aave v3 verdict as blanket approval of a new network instance or its assets.
• If activated, review each listed asset's bridge depth, oracle, caps, LTV, liquidation liquidity, and exit path.