Aave proposes 2-of-3 service-provider control for GHO Stewards

What happened

TokenLogic published an ARFC proposing that the GHO Risk Council Safe move from four individual signers with a 3-of-4 threshold to entity Safes controlled by Aave Labs, LlamaRisk, and TokenLogic with a 2-of-3 threshold.

What changed

The proposal creates a concrete path to lower the GHO Steward signing threshold and replace individual signing addresses with nested service-provider entity Safes. The candidate does not establish approval or execution.

What did not change

The GHO Risk Council Safe address would remain unchanged, as would the Steward contract role references and governance-defined bounds on Steward actions. No AIP is proposed because implementation would be a Safe owner-management transaction.

Confirmed

• The current configuration is described as 3-of-4 and the proposed configuration as 2-of-3.
• The proposed signer entities are Aave Labs, LlamaRisk, and TokenLogic.
• The GHO Risk Council Safe address is proposed to remain 0x8513e6F37dBc52De87b166980Fa3F50639694B60.
• The Steward contracts would continue referencing the same Safe address.

Still open

• Whether the ARFC will pass Snapshot.
• The internal signer thresholds and controls of each proposed entity Safe at execution time.
• Whether the current Council signers will execute the owner and threshold changes exactly as proposed.
• What additional coordination or segregation controls govern sensitive 2-of-3 Steward actions.

What it means for an advisor

• Monitor the Snapshot and the Safe owner-management transaction before treating the change as operative.
• If executed, review the Aave v3 memo's GHO control layer because two organizations rather than three individual signers could authorize bounded parameter actions.
• Document the nested entity-Safe thresholds and signer independence before deciding whether the current sleeve cap remains appropriate.
• Do not restrict the approved Ethereum GHO/sGHO position solely on this unapproved proposal.

Previous interpretation

The existing Aave v3 memo recognizes governance and steward controls but does not incorporate an executed 2-of-3 entity-Safe configuration for the GHO Stewards.