A repository for creating, managing, and submitting Aave Improvement Proposals (AIPs) to govern the Aave protocol.
Aave Improvement Proposals (AIP) is a repository and framework for creating and managing governance proposals for the Aave decentralized finance protocol. It standardizes the process of proposing changes—such as asset listings, parameter updates, or protocol upgrades—ensuring they are properly formatted, discussed, and submitted for on-chain voting. This system enables the Aave community to steer the protocol's development in a transparent and decentralized manner.
Aave community members, DAO participants, and developers who want to propose or review changes to the Aave protocol. This includes governance delegates, risk analysts, and smart contract engineers involved in DeFi governance.
It provides a well-defined, open-source process for protocol governance, reducing ambiguity and increasing participation. By integrating with Aave's governance infrastructure and offering clear templates, it lowers the barrier for submitting technically sound proposals while maintaining rigorous standards.
Aave Improvement Proposals
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides clear templates and formatting guidelines, as shown in the AIP template, ensuring all submissions are consistent and easy to review, reducing errors in governance processes.
Mandates discussion in Aave governance forums before submission, fostering consensus and reducing implementation risks, as emphasized in the contribution guide's ARC requirement.
Facilitates payload contracts for complex changes, with examples like AssetListingProposalGenericExecutor, enabling safe on-chain actions and reducing error-prone calldatas.
Hosts proposals on IPFS with preview links via the Aave governance interface, providing immutable and accessible records of all decisions, as listed in the AIPs table.
Requires Node v16 setup, dependency installation, and strict markdown formatting, which can deter non-developers and increase onboarding complexity for casual contributors.
Tightly coupled with Aave's specific governance tools and forums, making it unsuitable for other protocols and limiting adaptability to broader DAO use cases.
Involves cumbersome steps like forking the repo, managing image assets with full URLs, and creating PRs, which lack automation and could streamline submission.