veddnar

BGD will be leaving Aave governance.aave.com/t/bgd-leaving-…

An important update regarding Project E governance.aave.com/t/bgd-abandoni…

My $AAVE Alignment proposal: Ownership. If you are an $AAVE token holder, you should check it out governance.aave.com/t/arfc-aave-to…

I will write on the Aave governance forum more extensively about my view on the current debate surrounding Aave DAO and @aave Labs, but some points: - For a complex system like the Aave DAO to work and move forward, there needs to be frameworks of full transparency and control. And all contributors must abide by them, zero exceptions. - The upside of the Aave ecosystem should be majorly to AAVE token holders, to the Aave DAO. Whoever doesn't respect that is breaking the trust of the DAO and AAVE token holders. Considering that contributors are always generously compensated, it is pretty obvious to me that at least this type of principle is reasonable, and maximises the interests of AAVE holders. - "Real-world" legal frameworks sometimes are too slow to adapt to organisational innovations, so participants of a real DAO should have as a first principle an inherent loyalty duty towards the DAO. For example, in this case, if the Aave DAO doesn't have "in paper" ownership of aspects like a domain or communication channels, that doesn't mean any entity in practical control of those should monetise them directly or indirectly and asymmetrically to the detriment of the DAO, or should not have a responsibility on how to enable the DAO to have a say on them. - It is fine and desired for contributors to the DAO to build additional business. But if that business is mainly based on using channels that, due to its nature, the DAO has difficulty having/getting control over, the business is not in the best interests of the DAO. Doesn't mean the biz is not legally legitimate; it means it is misaligned with the DAO and control frameworks should protect against those unilateral decisions. - There really needs to be a serious discussion and DAO decisions on how/when "Aave" can be used, trying to represent the DAO and its token holders. It can't be that an organisation like the Aave DAO doesn't have strict guidelines about it, and private products can be promoted with it. - To be very clear, I think Aave Labs, in its current and previous shapes, brings value to the DAO and has the potential to keep doing it. But bringing value doesn't mean that it can be done in unilateral terms while using the Aave brand and name, without any type of control. It boils down to full transparency and simple frameworks based on good faith principles. Anti-fragility will do the rest.

Aave v3.6 is almost ready to be proposed to the Aave governance, and we have published all the details about it on the Aave DAO forum governance.aave.com/t/arfc-bgd-aav…

With the @ethereum Fusaka upgrade approaching, we have published a report on any potential effects on the Aave protocol. To summarise, NO negative impact is expected to be caused by the upgrade on Aave. governance.aave.com/t/bgd-technica…

It is now fully confirmed that the AAVE/wstETH Balancer v2 pool is NOT vulnerable, given that its implementation (Weighted pool) is different than the affected Composable Stable pools. Additionally, Balancer v3 pools are NOT affected, including boosted using Aave aTokens as underlyings.

👻 BGD 👻 Aave DAO 👻 Phase 6 ... and introducing Project E 🖐️ 👀 governance.aave.com/t/arfc-aave-bo…

Introducing Aave v3.6 👻 (link to forum below ⬇️)

Aave DAO <> BGD Phase 5 is ending! Check out a summary of our contribution during these last 6 months 👻 governance.aave.com/t/bgd-aave-bgd…

With Aave v3 more than 3 years in production, countless improvements done & ongoing, and v4 approaching its latest stage of development, we have published our vision regarding the Aave v3.X product going forward, and its relation with v4. Link and a summary below ⬇️

The Aave Protocol is v3.5 now

For all integrators of Aave v3, a reminder to subscribe to the aave_upgrades channel on Telegram to follow changes to the protocol's production systems. The BGD team is also reachable for any questions in the bgd-integrators channel on the Aave Discord

The Aave Protocol is v3.4 now

The Aave governance has approved the upgrade of the protocol from the current version (v3.3) to v3.4, and all payloads are scheduled to be executed tomorrow Thursday, July 3rd. Similar to previous upgrades, no action is required from users. vote.onaave.com/proposal/?prop…

👻 BGD 👻 Aave DAO 👻 Phase 5 governance.aave.com/t/arfc-aave-bo…

Aave DAO <> BGD Phase 4 has ended! Check out a summary of our contribution during these last 6 months 👻 governance.aave.com/t/bgd-aave-bgd…

If you are a @raycastapp Mac power user and want to access Aave's smart contract addresses, you can now! (link below 🔽)

If you are a senior backend developer and want to participate in the development of a multi-billion dollar DeFi system like Aave, reach out! x.com/i/jobs/1896852…

Aave is now v3.3