An interim update to the community, given the end of our engagement as of 31st March.
We have completed the majority of self-off-boarding work streams, including additional documentation, off-chain permissionless infrastructure migration, and coordination with different parties about the way forward on different projects (e.g., some described by Aave Labs HERE.
Currently, the following items are pending and will be performed during this week:
- The proposal for activation of Aave v3.7 across all networks, described HERE. While technically this will be performed outside of our scope, we believe it is a project that should be completed, as its offboarding to separate party will create too much inefficiency and risk.
Everything is currently ready on the activation side, so we estimate a matter of days until we create Phase 1 (networks with lower size). - Proposal for both cleaning deficit and increasing offset on Umbrella, as pre-approved HERE.
- Proposal for the transitional security retainer we announced HERE. This retainer will cover the period 1st April to 31st May, and we will already assume that role until the proposal passes.
- Different off-boarding coordination with contributors like @TokenLogic, @AaveLabs, and @ACI.
- Publish some extra documentation, e.g. Bored Guides.
- We will publish in this forum the recap of Aave <> BGD Phase 6.
Some extra clarifications:
- As of today, we are NOT under any type of official engagement with the Aave DAO/ecosystem in any area of contribution.
- The codebases of all user-facing tooling properties of the DAO have been migrated to the Aave DAO Github organisation. Any service provider/authorised-entity by the DAO is free to host them at their own will.
We will keep them temporarily hosted in our infrastructure, but down the line, we will potentially discontinue that, and we are NOT the maintainers of that infrastructure anymore. All the repositories have clear instructions on how to run and maintain, assuming certain technical expertise. - All service providers should, more than ever, take full ownership of their area of contribution. And whenever doing critical operational steps (e.g., proposals), apply proper testing and security procedures.