Skip to content

Latest commit

 

History

History
65 lines (46 loc) · 2.45 KB

v3-258-aave-v3-Ethereum-Lido-activate-gho-steward.md

File metadata and controls

65 lines (46 loc) · 2.45 KB

Proposal 258. Extend GHO Steward on Aave Prime Instance

Voting Link

Link to voting page

Governance Forum Discussion

Link to forum discussion

Payloads

Certora Analysis

Proposal Types

  • 🤝 Permission granting and revoking

Context

Following the development of the Gho steward and it's utilization on Arbitrum, this proposal seek to apply the steward on the Ethereum Prime (Lido) instance to manage the Gho token.

Proposal Creation

Transaction: 0xaee69532b473701cd2b3b14ec007396735aab17a67504860786cff3edc77b3c7

  • proposalId: 258
  • creator: 0x57ab7ee15cE5ECacB1aB84EE42D5A9d0d8112922
  • accessLevel: 1
  • ipfsHash: 0x8e8859a1ce499fdd4285610e9a833daf66da59c57af40469bad8aa110d33db88

createProposal() Parameters

{
    payloads: [
        {
            chain: "1",
            payloads_controller: "0xdAbad81aF85554E9ae636395611C58F7eC1aAEc5",
            payload_id: 251,
        },
    ],
    voting_portal: "0x9b24C168d6A76b5459B1d47071a54962a4df36c3",
    ipfs_hash: "0x8e8859a1ce499fdd4285610e9a833daf66da59c57af40469bad8aa110d33db88",
    access_level: 1,
}

Aave Seatbelt Report

Proposal Report

Link to Seatbelt proposal report

Payload Reports

Technical Analysis

We verified that the contract granted risk admin role is indeed the official aave-steward role. In addition, the old and currently used risk steward was restricted from managing the Gho token.

The proposal is consistent with the description on both Snapshot and the governance forum.

Certora validations

  • ✅ The code on the proposal payload corresponds to the proposal specification.
  • ✅ The proposal includes a proper tests suite, checking all necessary post-conditions.
  • ✅ BGD reviewed the payload before the proposal was submitted.
  • ✅ Certora reviewed the procedure followed to submit the proposal.