Gov v3 VotingMachine / VotingPortal maintenance
01Summary
Proposal to upgrade Aave Governance v3 Voting Machine smart contracts on Ethereum, Polygon, and Avalanche by deploying new DataWarehouse, VotingStrategy, and VotingPortal contracts. This involves registering new voting machines via approveSenders() on CrossChainController and adding new voting portals to the core Governance contract.
- Type
- contract upgrade
Key changes
- Deploy new VotingMachine contracts on Ethereum, Polygon, and Avalanche to replace non-upgradeable versions(high)
- Deploy new DataWarehouse and VotingStrategy contracts across all three networks(high)
- Register new VotingMachine contracts via approveSenders() on CrossChainController(high)
- Add new VotingPortals to core Governance contract on Ethereum for cross-chain communication(high)
Notable concerns
- Non-upgradeable contracts require full replacement rather than upgrades
- Changes affect voting infrastructure across three major networks (Ethereum, Polygon, Avalanche)
- Maintenance after 1+ year without changes to production contracts
Generated by Kvorum
02Description
Simple Summary
Proposal to make minor improvements on the Governance v3 VotingMachine smart contracts.
Motivation
After more than 1 year of working in production without changes, the Aave governance v3 Voting Machine smart contracts (Ethereum, Polygon, Avalanche) require minor maintenance to move them to an up-to-date state with the rest of the system, more precisely the a.DI (Aave Delivery Infrastructure) directly connected.
As they are not upgradeable, it is necessary to deploy new DataWarehouse contracts, new VotingStrategy contracts and new VotingPortals.
Specification
The governance proposal will call approveSenders() on the CrossChainController contract on every voting network (Ethereum, Polygon, Avalanche) to register the new VotingMachine contracts.
Additionally, addVotingPortals() will be called on the core Governance contract on Ethereum, with the new Voting Portals addresses, so that the Aave Governance can communicate with the new Voting Machines.
Voting Machines:
| Network | VotingMachine |
|---|---|
| Ethereum | 0x06a1795a88b82700896583e123F46BE43877bFb6 |
| Polygon | 0x44c8b753229006A8047A05b90379A7e92185E97C |
| Avalanche | 0x4D1863d22D0ED8579f8999388BCC833CB057C2d6 |
Voting Portals:
| Network Path | VotingPortals |
|---|---|
| Ethereum - Ethereum | 0x6ACe1Bf22D57a33863161bFDC851316Fb0442690 |
| Ethereum - Polygon | 0xFe4683C18aaad791B6AFDF0a8e1Ed5C6e2c9ecD6 |
| Ethereum - Avalanche | 0x9Ded9406f088C10621BE628EEFf40c1DF396c172 |
References
Copyright
Copyright and related rights waived via CC0.
03Mismatch analysis
A calldata-vs-description analysis is not generated yet. Review the decoded actions →
04Actions
This proposal carries no on-chain actions.
05Tally
Summed from votes
06Voters
No votes recorded yet.
07Forum
No forum thread is confidently linked to this proposal.
08Similar proposals
- aaveexecutedGov v3 VotingMachine / VotingPortal maintenance99%
- aaveexecutedRemoval of legacy VotingPortals from Governance v374%
- lidoexecutedOmnibus vote: 1) Remove the oracle member named 'Rated Labs' with address 0xec4bfbaf681eb505b94e4a7849877dc6c600ca3a from HashConsensus for AccountingOracle on Lido on Ethereum;64%
- lidoactiveOmnibus vote: 1) Remove the oracle member named 'Rated Labs' with address 0xec4bfbaf681eb505b94e4a7849877dc6c600ca3a from HashConsensus for AccountingOracle on Lido on Ethereum;63%
- lidoexecutedOmnibus vote: 1) Push new voting app version to Voting Repo 0x41D65FA420bBC714686E798a0eB0Df3799cEF092; 2) Upgrade the DAO Voting 0x2e59A20f205bB85a89C53f1936454680651E618e contract implementation; 3…62%
- lidoexecutedOmnibus vote: 1) Push new Voting app version to Voting Repo;59%