[MGC Decision] - AAVE 23, 24, and 26

Meta Governance Committee Decision:

AAVE 23

The Index Coop Meta-Gov Committee has voted unanimously (5-0) AGAINST listing AMPL on AAVE as part of AAVE-23. While we are generally supportive of listing new assets on AAVE there are several concerns we have with AMPL that we feel the need to vote against its inclusion in the AAVE market. AMPL’s status as a rebase token adds lots of complexity to its inclusion, including the creation of a custom aToken contract. We take smart contract risk seriously and the PeckShield audit raised several concerns, including an incorrect rebalance calculation, that cause us to call for further testing and transparency on said testing prior to inclusion. We would like to see a testnet integration for public testing of the new aToken contract, as well as full details of the local mainnet fork testing that was mentioned, including what was tested, how it was tested, and what the results were. Should these concerns be alleviated we would support a new AIP to include AMPL however at the present time out of an abundance of caution we are voting against inclusion. This vote will only take effect should the quorum not be reached.

FOR: [none]
AGAINST: @oneski22 @Kiba @Lavi @ncitron @cedrick
ABSTAIN: [none]

AAVE 24

The Index Coop Meta-Gov Committee has voted unanimously (5-0) FOR listing PAX on AAVE as part of AAVE-24. We are generally supportive of listing new assets on AAVE and PAX has several characteristics that make it prime for inclusion. PAX is one of only 2 fully regulated stablecoins and reserve attestations have shown it completely backed by cash and equivalents, as well as its assets being held separate from the operating funds of the parent company. This provides differentiation from existing stablecoins such as USDC and USDT. We support the addition of new options in the AAVE market and are happily voting for PAX’s inclusion.

This vote will only take effect should the quorum not be reached.

FOR: @oneski22 @Kiba @Lavi @ncitron @cedrick
AGAINST: [none]
ABSTAIN: [none]

AAVE 26

The Index Coop Meta-Gov Committee has voted unanimously (5-0) FOR continuing AAVE’s LM program as part of AAVE-26. We have seen firsthand as coop members the difficulty in coordinating changes to an LM program and the importance of their continuation unless an intentional stop has been voted on. We support AAVE continuing their program as they debate future changes to it.

This vote will only take effect should the quorum not be reached.

FOR: @oneski22 @Kiba @Lavi @ncitron @cedrick
AGAINST: [none]
ABSTAIN: [none]

14 Likes

RESPONSE FROM Naguib from Ampleforth in the Discord.

Hi all,

The custom Atoken was reworked after the initial Peckshield report. Peckshield performed a second round for the latest version with no findings. Also it has been extensively tested by both Ampleforth and AAVE teams.

Appreciate paying attention to the technical side. Here is the full picture of the implementation and its tests:

The PR with tests: Custom aAMPLToken by ahnaguib · Pull Request #66 · aave/protocol-v2 · GitHub
The token has been extensively tested here: protocol-v2/ampl-atoken.spec.ts at a0b270f160b241df7a7bd94a649563392d75c37f · aave/protocol-v2 · GitHub (20+ Scenarios)

The deployment on Kovan and Mainnet fork has been tested thoroughly through UI by both AAVE and Ampleforth teams. On kovan the deployment is run with accelerated rebases cycle to allow for testing different rebase scenarios in a short time span

1 Like

Further materials provided by Brandon from Ampleforth:

"
This could help give some context around the borrow/lend mechanics:

Or this older medium post:

"

2 Likes

Following the MGC decisions & per IIP-49, the following votes have been executed

AAVE-23 - NAY

AAVE 24 - YAE

2 Likes

Pretty cool to see this in action, really appreciate the follow up justification too. Congrats to the committee on getting these moved forward and keeping a Metagov clean sheet for the Coop!

6 Likes

AAVE-26 - YAE

source: Boardroom Management Portal

1 Like