[ARFC] Framework for ARFC and TEMP CHECK Proposals

---

Title: [ARFC] Framework for ARFC and TEMP CHECK Proposals Author: @MarcZeller - Aave Chan Initiative Date: 2023-06-27

Summary

This framework provides comprehensive guidelines for the Aave DAO community when creating and voting on ARFC (Aave Request for Comment) and TEMP CHECK proposals. It includes a template for crafting proposals and outlines the quorum and voting requirements.

Motivation

Distinction Between TEMP CHECK and ARFC

TEMP CHECKs serve as "temperature checks" to gauge community sentiment on a proposal or topic. They do not necessitate service provider involvement or a high level of precision or technicality.

Conversely, ARFCs are precursors to Aave Improvement Proposals (AIPs). Relevant service providers are formally invited to provide feedback on them, and the specification section of ARFCs should detail how the potential upcoming AIP will impact Aave protocol smart contracts.

Proposal Template

Each proposal must include the following sections:

A header:

1. Title: A concise and descriptive title for the proposal, including the proposal type (ARFC or TEMP CHECK) in a [TAG] format.
2. Author: The name of the author and/or entity creating the proposal.
3. Date: The date the proposal is being made, in the YYYY-MM-DD format.

A proposal body:

1. Summary: A succinct summary of the proposal.
2. Motivation: A detailed presentation of the proposal and potential benefits for the Aave protocol. This section can have sub-sections for improved readability.
3. Specification: A comprehensive description of the proposed change, including any relevant parameters or risk considerations. For ARFCs, this section should be technical, detailing the specific changes to be made. This section can have sub-sections for improved readability.
4. Disclaimer: Any necessary disclaimers, such as conflicts of interest or third-party involvement.
5. Next Steps: The proposed next steps if the proposal is approved.
6. Copyright: A statement defining proposal copyright. While Open-Source is mandatory, the choice of a specific license is left to the author.

Voting Guidelines

1. Vote Start Time: The vote should commence 24 hours after the proposal is published on Snapshot.
2. Proposal Age: The governance thread related to the snapshot vote should be at least 5 days old before voting begins.
3. Vote Duration: The vote should last for a minimum of 3 days.
4. Vote Options: The vote should have at least three options: YAE (Yes), NAY (No), and ABSTAIN.
5. Quorum: The vote should reach a quorum of 320,000 YAE votes.
6. Differential: The YAE votes should exceed the second-largest vote option (either NAY or ABSTAIN) by at least 80,000.

Proposal Cycle:

Special Considerations

This framework should be considered as a general template for general proposals. Specific proposals and/or frameworks, such as asset onboarding or caps updates, should follow specific guidelines as determined by the Aave DAO community.

This framework is designed to ensure that all proposals are thoroughly considered and that all votes are fair and representative of the Aave DAO community's views.

Specification

As this proposal pertains to governance guidelines, it does not require any on-chain action or protocol change.

Disclaimer

The ACI is not presenting this ARFC on behalf of any third party and is not compensated for creating this ARFC.

Next Steps

1. If consensus is reached on this ARFC, escalate this proposal to the Snapshot stage.
2. If the Snapshot outcome is YAE, this proposal will be considered canon, and the guidelines will be adopted.

Copyright

Copyright and related rights waived via CC0.