Aave opens the final on-chain vote to activate v3.3 on Sonic

What happened

Aave governance created proposal 257 to activate an Aave v3.3 pool on Sonic with USDC, WETH, and wS.

What changed

The earlier deployment concept advanced to an executable on-chain proposal with initial collateral, borrowing, caps, liquidation parameters, oracle choices, and bootstrap administrator assignments.

What did not change

The proposal had not passed or executed by February 28, so it did not create a live advisor-accessible Sonic exposure inside this backfill window.

Confirmed

• Proposal 257 was created on February 26, 2025.
• It proposed listing USDC, WETH, and wS as borrowable collateral on Sonic.
• It proposed assigning the risk steward as RiskAdmin, the guardian as PoolAdmin during bootstrap, and the ACI multisig as emissions admin.

Still open

• The vote outcome and any execution occurred outside the February event-date boundary and are not drafted here.
• Live liquidity, operational performance, and bridge and oracle dependency behavior were not established within the window.

What it means for an advisor

• Update the Aave diligence file to track the concrete Sonic configuration while keeping Sonic outside the approved exposure set pending execution and live-operation evidence.
• Review the proposed bootstrap admin roles, oracle choices, and asset caps before any later access decision.

Previous interpretation

The January backfill recorded that Aave had advanced a proposed v3 deployment on Sonic, without a final executable activation payload.