Summary
As we commented on our governance update about leaving Aave once our current engagement finishes, before that happens, we will publish different extra documentation oriented to the technical procedures of different Aave ecosystem products we are contributing to.
Consequently, we have created a Bored Guides repository on the Aave DAO Github organisation, where we will upload all different intended guides progressively.
The Bored Guides
In addition to the GitHub repository, we will list the guides in this thread, updating the following table whenever a new one is added. The initial guide included in the repository is regarding all procedures surrounding the activation of a.DI (Aave Delivery Infrastructure) and Aave Governance on new networks, pre-requirement to expand the GHO stablecoin and the Aave Protocol itself.
| Guide | Description |
|---|---|
| a.DI/Governance network expansions | Procedure for expanding a.DI and Aave Governance to new networks |
| Aave Seatbelt | Native documentation of the Aave Seatbelt tool, used to simulate and verify changes to Aave through governance proposals or similar architectures |
| Aave custom price feeds | Procedure for deploying and maintaining custom price feeds used on the Aave protocol |
| Aave Proof of Reserve | Procedure for the Proof of Reserve system used on the Aave protocol |
| Aave onchain rewards management | High-level overview and procedures for Aave v3 and Umbrella on-chain rewards management |
| Umbrella maintenance and expansion | Maintenance and expansion guide for Aave Umbrella |
| Aave v3 asset listings procedure | Overview of the procedure to list assets on Aave v3 |
| Aave v3 network evaluation/expansion procedure | High-level procedures for Aave v3 network expansions |
| Risk agents maintenance-expansion | Guide for maintenance and expansion of risk agents |
| Aave Robots overview | High-level overview and maintenance of Aave Robots (automations) |
Disclaimers
- These guides are high-level descriptions of different procedures, with varying depth of detail. Whoever applies them MUST understand the context of application and have sufficient technical and product expertise.
- All procedures and guides are ever-growing, organic documents that the elected maintainer should keep updated.
- These guides do NOT guarantee 100% correctness or completeness of any procedure. BGD Labs (or other contributors) assumes no liability for misapplication and/or lack of expertise when executing a flow using a guide as a reference.