Aave executes USDe and sUSDe onboarding on Avalanche

What happened

Aave governance executed proposal 397, onboarding USDe and sUSDe to the Aave V3 Avalanche instance.

What changed

USDe and sUSDe became configured collateral reserves on Avalanche with 50 million-unit supply caps, dedicated capped-oracle paths, and stablecoin E-mode configurations. USDe was enabled for borrowing while sUSDe was not.

What did not change

Execution did not expand Ketju's Ethereum-only Aave approval, establish advisor suitability for either asset, or demonstrate sustained liquidity and liquidation performance on Avalanche.

Confirmed

• Aave proposal 397 reached executed status on October 25.
• The executed proposal configured 50,000,000-unit supply caps for both USDe and sUSDe.
• USDe was configured as borrowable; sUSDe was configured as non-borrowable.
• Both assets were enabled as collateral and assigned capped-oracle configurations.

Still open

• Live reserve liquidity, utilization, borrower concentration, and liquidation performance after onboarding.
• The assets' suitability for any future chain-specific Ketju approval.

What it means for an advisor

• Add the Avalanche reserves to Aave's cross-chain diligence perimeter and monitor their oracle and liquidation performance.
• Do not treat execution as an expansion of the approved Ethereum Aave sleeve.