Reading time saved: 2 minutes
8 replies, 2581 views, 17 likes
The Aave DAO community largely supports a policy change proposed by Llamaxyz to halt listings on all Aave v1 and v2 non-permissioned deployments and transition to v3, but the initial proposal failed to meet the quorum due to low voter turnout. A re-run of the vote has been confirmed to encourage more community participation.
The discussion revolved around a policy change proposed by Llamaxyz for the Aave DAO, which aimed to halt listings on all Aave v1 and v2 non-permissioned deployments as part of the transition to v3. The proposal suggested that future asset listings should only occur on Aave v3 deployments, excluding the Aave ARC and Centrifuge RWA markets which use the "Permissioned" V2 codebase. The proposal also stated that no further assets would be added to any of the Aave Market pools upon successful voting on Snapshot to implement this upgrade. A Snapshot vote was scheduled to commence on the 1st December 1.
The proposal received support from several community members including Kene_StableLab and MarcZeller, who both agreed that it was time to push for Aave V3 adoption 2,6. However, Fig raised a question about the criteria for a successful Snapshot vote, suggesting the need for clearer rules 3. Llamaxyz later announced the creation of a Snapshot for the proposal, with voting scheduled from 5th to 9th December 4. Despite the support, the proposal failed to meet the quorum due to a lack of voter participation, leading to a suggestion for a re-run by MarcZeller 8. Llamaxyz confirmed a re-run of the vote and encouraged participation 9.
In conclusion, the community is largely supportive of the transition to Aave v3, but the initial proposal failed to meet the quorum due to insufficient voter participation. A re-run of the vote has been confirmed, and community members are encouraged to participate in the decision-making process.
Posted a year ago
Last reply a year ago
Summary updated 2 months ago
Last updated 08/12 04:39