title: [ARFC] GHO Stewards Signer Update
author: @TokenLogic
created: 2026-08-05
Summary
This proposal updates the signer set of the GHO Stewards admin role, the operator of the GHO Steward contracts, to a 2-of-3 configuration consisting of LlamaRisk, TokenLogic, and Aave Labs.
Motivation
Overview
The GHO Risk Council operates the GHO Steward contracts (GhoAaveSteward, GhoBucketSteward, GhoGsmSteward, and GhoCcipSteward), which enable timely, bounded parameter adjustments for GHO within limits defined by governance.
Over recent months, the Safes managing the DAO’s finances, including the Aave Finance Committee, have converged on a common 2-of-3 signer configuration. Upon implementation, this publication will replace Individual’s signers with Service Provider owned signing addresses.
The Gho Risk Council remit is functionally limited to the various Steward Roles as defined in Governance V2 and assigned by tokenholder votes.
Please note that, prior to this publication, the legacy Chaos Labs address was transitioned to an Aave Labs address.
We extend our sincere thanks to each of the Steward signers, whose responsiveness and diligence have supported GHO’s parameter management since the Council’s inception.
Rationale for the Signer Update
Adopting the shared configuration provides:
- General Updates: updating signer addresses to reflect those actively contributing to the Aave ecosystem.
- Signer Continuity: Each contributing organization manages its own internal signer roster within its entity Safe, so personnel changes no longer require per committee signer rotations. If a service provider were to leave Aave abruptly, the Steward role can continue to function, preserving confidence in the governance of the GHO ecosystem.
- Operational efficiency: A 2-of-3 threshold across three highly available service providers preserves the Council’s ability to act within the response windows that the Steward contracts assume.
The Council Safe address is unchanged. The GHO Steward contracts reference the Safe address, not its signers, so no change to any Steward contract or on chain permission is required.
Specification
The signer update applies to the GHO Risk Council Safe across each network where the Steward role is active:
| Item | Current | Proposed |
|---|---|---|
| Safe Address | 0x8513e6F37dBc52De87b166980Fa3F50639694B60 | Unchanged |
| Threshold | 3 of 4 | 2 of 3 |
| Signers | Individual signer addresses | Entity Safes (below) |
Proposed signer set:
| Entity | Address |
|---|---|
| Aave Labs | 0x4b752551fC6345A7de82F76fd7a5015CA16d1a74 |
| LlamaRisk | 0xb291232F480F41c75802C4a60F1D2AC03404Afef |
| TokenLogic | 0x9DE1d45e2786b03498289959203F25b29B4D1193 |
The update will be executed as a standard Safe owner management transaction signed by the current Council signers. No Aave governance payload is required as the Council Safe address, and therefore the RISK_COUNCIL reference in each GHO Steward contract, is unchanged.
Disclaimer
TokenLogic is an active service provider to the Aave DAO, the beneficiary of stream 100086 and the KPI as outlined in this publication. The scope of this engagement is available via this forum proposal.
TokenLogic supports and maintains an independent delegate voting platform within the Aave community.
TokenLogic and associated entities have no undisclosed material conflicts of interest at the time of submission.
Next Steps
- Gather feedback from the community.
- If consensus is reached on this ARFC, escalate this proposal to the Snapshot stage.
- If the Snapshot outcome is YAE, the signer update will be executed by the current Council signers. No AIP is required as no on-chain governance action is involved.
Copyright
Copyright and related rights waived via CC0.