Aave Improvement Proposal (AIP) may be created and submitted by any community member who has sufficient proposition power. Its recommend to start with an ARC to gather rough consensus on the governance forums, then move to the AIP phase.
The AIP number will be assigned by an AIP reviewer, and the AIP status should start at
WIP (Work In Progress).
Once the AIP is written and polished, it needs to be submitted via Github by forking the AIP repository and following the instructions there.
Once the AIP pull request has been polished and reviewed, it becomes ready for on-chain governance. This requires the following technical steps:
The reviewed AIP is merged into the AIP repository and passes the CI pipeline (currently performed by the Aave Genesis Team).
The reviewed AIP is parsed and uploaded to IPFS. We recommend using the AIP uploader tool. The returned IPFS hash is needed for the next step.
The payload is reviewed and sufficiently tested.
A community member with enough proposition power is now able to submit the AIP for on-chain governance.
Currently this is a technical process, so requires a developer to submit the payload and IPFS hash using the
create() function on Governance v2 with the appropriate parameters.