BGD. Leaving Aave

Development
22

Seeing this makes me really sad. @MarcZeller should take responsibility for coordinating and helping BGD Labs and Aave Labs reach a reconciliation.

3 Likes
23

@BGDLabs , let’s cut to the chase. The political games and governance capture by Labs and Stani are completely out in the open. When one entity controls all the levers and holds the protocol hostage, acting democratically is mathematically impossible.

I have one direct question for you: Are you open to participating in a Community Fork of the V3 codebase alongside ACI?

I challenge @MarcZeller to run a poll on X (Twitter) right now. You will instantly see that the silent majority of this community supports a fork over remaining in this toxic environment. We would appreciate it if you could share your definitive stance on this.

24

Let’s try to find a way on how to get back together. Let’s find a way to make AAVE itself as the community protocol. No new fork is required imo.

2 Likes
25

Last statement from BGD was loud and clear…

You suggest something they aren’t ready to reconsider, unfortunately.

1 Like
26

At TokenLogic, we’ve had the privilege of working side by side with the team at BGD Labs for a long time, we have been close collaborators and become good friends.

Their impact on the Aave Protocol speaks for itself. From leading the architecture and evolution of Aave V3, to delivering Umbrella, to orchestrating multi-chain deployments and maintaining robust governance infrastructure, BGD consistently operated at an exceptional technical standard. The reliability, security mindset, and operational discipline they brought to every initiative strengthened the foundation of the entire ecosystem.

What stands out most to us, however, is how they approached the work. Thoughtful in discussion, principled in decision-making, and unwavering in their commitment to what serves the protocol best, they set a tone that elevated everyone building alongside them.

The Aave ecosystem is materially stronger because of BGD’s dedication and craftsmanship. We’re grateful not only for what they’ve built, but for the partnership and friendship we’ve built together along the way.

We’re excited to see what they do next and will always appreciate everything they’ve contributed.

11 Likes
27

It is SAD , no doubt about it!

As Stani said this is the end of an old chapter , and I still hope there is still room for BGD in the AAVE new chapters.

28

For reference related to our off-boarding, we have started publishing the Aave Bored Guides. More information BGD. Aave Bored Guides

1 Like
29

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.
15 Likes