Close Menu
FSNN | Free Speech News NetworkFSNN | Free Speech News Network
  • Home
  • News
    • Politics
    • Legal & Courts
    • Tech & Big Tech
    • Campus & Education
    • Media & Culture
    • Global Free Speech
  • Opinions
    • Debates
  • Video/Live
  • Community
  • Freedom Index
  • About
    • Mission
    • Contact
    • Support
Trending

The CDC Doesn’t Want You To See A CDC Report On How Effective COVID Vaccines Are

8 minutes ago

State vs. Local, State vs. State

10 minutes ago

Artemis and the Lunar Frontier

32 minutes ago
Facebook X (Twitter) Instagram
Facebook X (Twitter) Discord Telegram
FSNN | Free Speech News NetworkFSNN | Free Speech News Network
Market Data Newsletter
Wednesday, April 15
  • Home
  • News
    • Politics
    • Legal & Courts
    • Tech & Big Tech
    • Campus & Education
    • Media & Culture
    • Global Free Speech
  • Opinions
    • Debates
  • Video/Live
  • Community
  • Freedom Index
  • About
    • Mission
    • Contact
    • Support
FSNN | Free Speech News NetworkFSNN | Free Speech News Network
Home»Cryptocurrency & Free Speech Finance»Core Technical Contributor to Cease Involvement with Aave DAO
Cryptocurrency & Free Speech Finance

Core Technical Contributor to Cease Involvement with Aave DAO

News RoomBy News Room2 months agoNo Comments3 Mins Read786 Views
Share Facebook Twitter Pinterest Copy Link LinkedIn Tumblr Email VKontakte Telegram
Core Technical Contributor to Cease Involvement with Aave DAO
Share
Facebook Twitter Pinterest Email Copy Link

Listen to the article

0:00
0:00

Key Takeaways

Playback Speed

Select a Voice

BGD Labs, a core technical contributor to decentralized finance protocol Aave, said it will conclude its involvement with the project’s DAO on April 1 after four years.

In a Friday forum post on Aave, BGD cited an “asymmetric organizational scenario,” which it said the DAO has “badly executed” without consideration of contributors’ expertise. The contributor added that Aave had taken an “adversarial position” of the third version (v3) of its protocol to promote features in the fourth (v4).

“While all previous points that BGD should just keep contributing on the v3 side exclusively, the situation created makes it nonsensical to us: every time we think/will think about improving v3, there will be some type of implicit/explicit artificial constraint,” said BGD. “We are not really interested in being in that position, as we think it is a waste of our potential.”