The Aave v3.X BGD’s Vision

[Sachi]

To summarize the above discussion, I believe the main concerns come from the below points:

1. The codebase of V4 has been released and communicated very recently to SPs.

@bgdlabs

Aave v4 until very recently has been developed privately by Aave Labs.

@MarcZeller

Service providers were informed of the v4 codebase literally only days ago.

And it’s further confirmed and proposed by @Emilio

@Emilio

We will do our best to improve communication and try to do things as transparently as possible while we approach the final steps towards the V4 release.

Going forward, it’d be beneficial for all SPs being communicated for intended release schedule in advance, especially for important product like V4. Would you suggest some pre-communication time frame so that SPs could have time for independent reflection and adding value? @bgdlabs @MarcZeller @Emilio

2. V3 off boarding timeline:

@MarcZeller

V3 is the largest defi protocol on earth, freezing improvement and development is doing a favor to competition that won’t casually sit on a bench while v4 gets ready.

@bgdlabs

Aave v3.X and Aave v4 should be treated by the DAO as independent projects, not really understood as the continuation of the other, just different. If they converge down the line, this should just happen organically, but not forcefully. Aave v4 should NOT replace v3.X anyhow.

@JosueMpia

Mid-2027: Begin soft unwind for v3.

@Emilio

there was never any intention, by Aave Labs, to try and push for an immediate offboarding of V3 - that would be unwise and outright dangerous

Thus it is unanimous regarding the phase out of V3. To summarize, starting from now on, we will revisit and decide on the off boarding of V3 only after 2 years (Sep 2027).

3. V4 officially on boarding (flippening) time:

@bgdlabs

We don’t really see any scenario where, let’s say, after 1 year, the DAO doesn’t decide to prioritise v4 if that’s the desire. Because that would have meant that during 1 year v4 didn’t show success, or that its features didn’t fit with the market, which we have no reason to think it is the case.
Moreover, in some type of optimistic scenario, it could be that soft steps prioritising v4 instead of v3 could start way earlier, e.g., 6 months after v4 release, or any shorter timeline.

@MarcZeller

if there’s a V4 “flippening” it won’t happen realistically before the later stages of 2026.

@JosueMpia

Aave v4 over time will become the main focus as the ecosystem shifts toward it. Maybe by the end of 2026, v4 will really start to show its dominance, but for now Aave v3 remains essential.

I here summarize everyone’s opinion as following:

BGD: 12 months

MarcZeller: 12 months

JosueMpia: 16 months

Average : 12.4 months

note: I allocate 0.55 weight out of 1 to BGD, 0.35 to Marc Zeller and 0.1 to JosueMpia

[MarcZeller]

@Sachi

Going forward, it’d be beneficial for all SPs being communicated for intended release schedule in advance, especially for important product like V4. Would you suggest some pre-communication time frame so that SPs could have time for independent reflection and adding value? @bgdlabs @MarcZeller @Emilio

I would like to echo this sentiment, there’s a generalized feeling of a lack of communication between Aave Labs and the rest of the SPs operating and maintaining the day-to-day of the Aave protocol, this leads to unwanted outcomes and miscommunications.

[stani]

We outlined the next steps during our first internal session for the SPs in Cannes last June and explained that the codebase had reached feature completion, transitioning into the security hardening phase. In August, we hosted a code walkthrough that all other SPs, including ACI, were invited to join and ask questions. The session was well received and generated very positive feedback. More recently, just last week, we conducted another round of code introductions and a risk primer for the Aave DAO SPs.

Throughout the process, development has been guided by monthly transparent updates, culminating most recently in the Aave V4 development update, which clearly highlights the upcoming milestones.

We deeply appreciate the enthusiasm to see Aave V4 released as soon as possible. However, we must prioritize safety and ensure thorough security hardening before setting a launch date, which we hope to establish in due course.

[EzR3aL]

It’s a bit off topic I guess, but what if there was a monthly SP & Orbit delegate call to discuss important topics?

[Kene_StableLab]

@EzR3aL We used to have Governance Calls; it was part of a grant awarded to Boardroom. I think this would be a very important practice to reignite. From our end, we would be down to support this.