Aave

Authors: @Kene_StableNode & @MarcZeller (Aave Chan Initiative)

GLOSSARY

ARFC: Aave Request for Final Comments (ARFCs)

ARC: Aave Request for Comments (ARCs)

AIP: Aave Improvement Proposal (AIP)

TEMP CHECK: Temperature Check

Simple Summary

The Aave Governance Process Improvements proposal introduces changes to the current governance process to create a more agile and robust process.

Abstract

According to the Aave Governance Process, there is no clear distinction on which kind of proposals govern different aspects of the Aave Protocol. There are ARCs, ARFCs and AIPs that govern all aspects of the Aave Protocol.

This proposal aims to streamline the Aave Governance Process by renaming ARCs to become known as TEMP CHECKs and clearly defining the specific kinds of proposals that are TEMP CHECKs and which kinds of proposals will be regarded as ARFCs.

Motivation

Due to the lack of a clear distinction between the proposals in Aave Governance, the Aave Governance Process is overwhelmed by proposals which could have shorter proposal timelines because they have been previously discussed and form part of the day-to-day operations of the Aave DAO.

This proposal is intended to shorten the lifecycle for mature proposals involving Risk Service Providers’ direct involvement while clearly distinguishing which proposals have to pass through the entire Aave Governance Process to enable ample community feedback and participation.

Specification

TEMP CHECKs shall become the first step in the Aave Governance Process; if a proposal falls into the scope of a TEMP CHECK as defined below, then the proposal shall start as a TEMP CHECK, and after the TEMP CHECK phase, the proposal shall be submitted as an ARFC before becoming an AIP.

However, where a proposal does not fall under the TEMP CHECK scope, the proposal will be regarded as an ARFC and subsequently become an AIP.

Amendments

We recommend the renaming of ARCs to become known as TEMP CHECKs.

Proposal Distinctions

TEMP CHECKS

Any proposal which falls under the scope outlined below will be known as a TEMP CHECK, and the title of the proposal must contain “TEMP CHECK”. TEMP CHECKs are proposal conversation starters which do not require input from Aave DAO Service Providers.

Any discussion which requires general community feedback. Discussing listing of Assets not previously listed in any Aave Market. Any proposal which involves deploying Aave on a new network. Any discussion or proposal which involves the assessment of GHO Facilitator candidates. Any discussion or proposal which involves the assessment of Portals Operator candidates. Any discussion or proposal which involves the assessment of New Service Provider Candidates. ARFCs

These refer to mature and significant technical proposals which require the input of Aave DAO Risk Service Providers. The format of an ARFC must align with the format of an AIP, which will be escalated to Snapshot and subsequently On-Chain Aave Governance.

The following proposals fall within the scope of an ARFC:

Risk Parameter Changes of currently onboarded assets. A proposal involving the onboarding of an asset which is already onboarded on an Aave Market. Any proposal involving the renewal of a previously engaged Aave Service Provider.

NB: It is important to note that the Fast Track 2 & Direct to AIP shortcuts, such as the Caps Update Framework 1, are still valid under this amendment; these shortcuts are designed to enable quick mechanical improvements of the Aave Protocol.