Aave proposes Governance Emergency Guardian signer rotation

What happened

Aave Labs published an ARFC proposing a new nine-address signer roster for the Governance Emergency Guardian.

What changed

A concrete signer-rotation proposal now exists for the multisig that can cancel malicious, erroneous, or unsafe governance proposals and payloads. No operative owner rotation is established by this record.

What did not change

The proposal retains the existing 5-of-9 threshold, Governance Emergency Guardian Safe addresses, assigned cancellation permissions, and exercise conditions. It does not show Snapshot approval, AIP approval, or executed Safe owner transactions.

Confirmed

• The proposed guardian remains a 5-of-9 multisig.
• The proposal identifies nine replacement or retained signing addresses.
• Existing Safe addresses and Governance and PayloadsController permissions are proposed to remain unchanged.
• A chain-by-chain execution manifest is expected before implementation.

Still open

• Whether the ARFC will receive favorable community sentiment and Snapshot approval.
• Whether every proposed signer will confirm operational readiness.
• The final chain-by-chain execution manifest and resulting on-chain Safe owner sets.

What it means for an advisor

• Keep the Aave v3 memo unchanged while the proposal remains unapproved and unexecuted.
• Monitor the Snapshot, execution manifest, and each Safe owner-management transaction.
• Reopen the control review if implementation changes a Safe address, threshold, cancellation authority, or other permission beyond the stated signer rotation.

Previous interpretation

The Aave v3 memo treats this as a signer-only proposal that does not fire its emergency-powers kill criterion because the threshold, Safe addresses, and powers remain unchanged.