> For the complete documentation index, see [llms.txt](https://contributions.ryanholloway.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://contributions.ryanholloway.xyz/rabbithole/rh-metagov/voting-recs/aave-approve-v3-deployment-governance-framework.md). # Aave: Approve V3 Deployment Governance Framework Voting Recommendation by (Discord: Raho#0007) ## **Summary:** There is currently a lot of demand for Aave deployments across various EVM compatible blockchains/L2’s. If passed, this proposal will essentially standardize the practice for the deployment of Aave V3 onto new chains. Due to the fact that deploying Aave onto a new chain comes with costs such as time, monetary costs, and some risk, it is important for the Aave community to develop a framework for deploying onto new chains. The proposed framework can be found here: - Proposed Framework Benefits: ``` > - Standard governance process Framework. - Minimum delay of 5 days between Network governance proposal in the governance forum and creation of a snapshot vote. - Minimum quorum of 150k AAVE votes to consider the proposal as adopted. > ``` **Proposal:** ### **Recommendation:** I recommend that the Rabbithole metagovernance pod vote ‘Yes’ on this proposal. With the expansion of Aave onto new chains, I believe that a framework for filtering deployment proposals is necessary. This framework will increase governance efficiency, and also set a standard for risk when proposing to deploy Aave to new chains. I believe this is positive sum, as it will set an ongoing standard for Aave, and gives users peace of mind on any chain that they use Aave on! **Open Questions:** Will this be enforced? if so, how? **Feedback:** **Execution status:** Executed **Vote:** Yes. **Community Vote** * 19 Y * 0 N **Pod Vote** * 21 Y * 0 N