Aave v3 Ethereum. Approval of path forward
Following the community discussion opened on the Aave governance forum https://governance.aave.com/t/bgd-aave-v3-ethereum-new-deployment-vs-aave-v2-upgrade/9990, the goal of this vote is for the Aave community to decide a path forward in what regards doing a “clean” deployment of Aave v3 in Ethereum versus upgrading the Aave v2 Ethereum smart contracts to a v3 version. It is really recommended to review the analysis on the forum before emitting a vote.
In practice, this vote will authorize BGD Labs to proceed with the chosen option (if any), engineering-wise, as part of the working scope with the Aave community.
The options are:
- Deploy a new Aave v3 Ethereum: do a “clean” new deployment, with v2 and v3 Ethereum living together, separately.
- Upgrade v2 contracts to v3: upgrade the v2 smart contracts to v3, with no new deployment.
- No decision; more discussion: keep discussing on the Aave governance forum about the path forward.
| Voter | Cast Power | Vote & Rationale |
|---|---|---|
 FranklinDAO (Prev. Penn Blockchain) | 95,047 | Deploy a new Aave v3 Ethereum |
 0xdC1F...f5E432 | 95,000 | Deploy a new Aave v3 Ethereum |
 0x62a4...96816a | 86,003 | Deploy a new Aave v3 Ethereum |
 0xB83b...Fbcf5C | 85,000 | Deploy a new Aave v3 Ethereum |
 0x55B1...09f262 | 68,820 | Deploy a new Aave v3 Ethereum |
VOTE POWER
Proposal Status
- Tue October 04 2022, 10:00 amVoting Period Starts
- Tue October 11 2022, 10:00 amEnd Voting Period
Current Results
1-Deploy a new Aave v3 Ethereum
521,860.902
2-Upgrade v2 contracts to v3
619.101
3-No decision; more discussion
17.663