Title: [ARFC] Network deployment ARFC template
Authors: @Kene_StableLab, @MarcZeller - Aave-Chan Initiative
Date: 2023-04-05
Simple Summary
In line with the amendments made to the Aave Governance process, it is imperative to introduce an ARFC Template for deploying Aave on a new Network; this proposal aims to set the standard for deploying Aave on new networks.
Motivation
Creating Standards is essential to improving the Aave Governance Process; through this template proposal, we hope to begin the first step in implementing several standards that will form the foundation for how proposals in various categories are written before being presented to the Aave DAO.
Specification
Upon passing this proposal, all prospective proposal authors will be required to follow the Network Deployment Template, as stipulated in the Appendix of this proposal.
Disclaimer
The Aave-Chan Initiative (ACI) & StableLabs are not compensated in any form for creating this ARFC proposal. This ARFC has been prepared solely to facilitate community discussion.
Next Steps
- Gather feedback and input from the Aave community on the proposed Network Deployment Template.
- Refine the template based on community feedback.
- If consensus is reached and the template is refined, submit the ARFC for a snapshot vote for final approval.
Copyright
Copyright and related rights waived via CC0. You are free to share and adapt the content, as long as you give appropriate credit, provide a link to the license, and indicate if changes were made.
Appendix
ARFC New Network deployment template
Title: [ARFC] Aave Deployment on [Candidate Network]
Author: [Author Name/Username] - [Organization, if Any]
Date:
The date the ARFC is submitted, using the [Date: YYYY-MM-DD] format in the header. This allows for a clear and consistent reference point throughout the Aave governance process.
Summary:
A brief description of the ARFC goal with a mention of the candidate network to deploy Aave on and the version of Aave.
Abstract:
A concise summary of the proposal outlining deployment proposal, specifying the asset selection and deployment chain.
Motivation:
A comprehensive overview of the reasons for proposing the deployment, outlining the benefits and potential impact on both Aave and the candidate network ecosystems.
Specification:
A detailed breakdown of the proposed deployment, including asset selection, risk parameters, and any other relevant information specific to the candidate network.
This section will contain a detailed table with the candidates’ assets for the deployment and recommended risk parameters.
The author can update this section with Risk service providers’ feedback.
Deployment Checklist:
A list of required actions to ensure a successful deployment, including:
- Feedback from at least one Risk Service Provider (Gauntlet or Chaos Labs)
or 
- Infrastructure/technical evaluation report by BGD Labs or
- Oracle recommendation (For example: Chainlink or
- The graph support or
The author can update this section with feedback from the ARFC discussions.
Disclaimer:
A mandatory statement that clarifies the author’s relationship with the proposed deployment, any potential conflicts of interest, and any holdings. This section ensures transparency and provides context for the community’s discussion.
Next Steps:
A clear outline of the steps to be followed after the submission of the ARFC, including community feedback, refinement, snapshot voting, and the final approval process.
Copyright:
ARFC authors are invited to open-source their work but not setting CC0 as mandatory, alternative open-source license can be set.