Aave proposes USDai and sUSDai onboarding on Arbitrum

What happened

An Aave ARFC proposed onboarding USDai and sUSDai to the Arbitrum V3 instance with supply caps, a USDai borrow cap, CAPO settings, and isolated E-mode collateral configurations.

What changed

A concrete pathway was proposed for Aave to accept exposure connected to the rejected USD.AI credit product, requiring cross-memo review before any implementation.

What did not change

The ARFC did not execute an AIP, activate either reserve, extend Ketju approval to the assets, or establish that the proposed parameters became operative.

Confirmed

• The proposal specifies 55 million supply caps for both USDai and sUSDai.
• It specifies a 45 million borrow cap for USDai.
• The proposed sUSDai/USDai E-mode uses 89% LTV and a 91% liquidation threshold.
• The proposed sUSDai stablecoin E-mode uses 88% LTV and a 90% liquidation threshold.
• The proposal says a successful ARFC would require a later AIP for final confirmation and enforcement.

Still open

• The ARFC vote result and any subsequent AIP or execution are not established.
• The proposal's top-level borrowability table conflicts with its borrow-cap and E-mode specifications for USDai.
• No executed reserve configuration, oracle address, liquidity assessment, or deployed CAPO configuration is supplied.

What it means for an advisor

• Review the Aave v3 memo for potential leakage of rejected USD.AI credit exposure through collateral and E-mode pathways.
• Keep USDai and sUSDai outside approved Aave allocations unless a later executed payload receives asset-specific review.
• Reconcile the contradictory borrowability specifications before evaluating any final AIP.