Connect with us

Crypto World

Aave’s “Civil War” Claims First Casualty as Key Developer Walks Away

Published

on

Aave’s “Civil War” Claims First Casualty as Key Developer Walks Away

A long-running governance dispute inside the Aave ecosystem has escalated after a core engineering firm announced it will step aside.

Key Takeaways:

  • Core developer BGD will not renew its contract, deepening a governance dispute between Aave DAO and Aave Labs.
  • The conflict centers on plans to push users from Aave v3 to the upcoming v4 upgrade.
  • The announcement rattled the market, with the Aave token dropping over 6%.

Bored Ghosts Developing (BGD), a software company contracted by Aave DAO to build and maintain key components of the lending protocol, said Friday it will not renew its agreement when the current term expires in April.

In a post on Aave’s governance forum, the team blamed Aave Labs, the company founded by protocol creator Stani Kulechov, for pushing a strategic shift tied to the upcoming Aave v4 upgrade.

Aave Developer Refuses to Support V3 Amid Push Toward V4

Advertisement

BGD said it could not continue work on Aave v3 while efforts were underway to steer users toward the new version.

“We believe even proposing this on the main revenue-maker & fully functional engine of Aave is borderline outrageous,” the group wrote.

The market reacted quickly. The Aave token fell more than 6% following the announcement.

Kulechov acknowledged the departure, writing on social media that the team had played a critical role in the protocol’s development.

Advertisement

BGD co-founder Ernesto Boado previously served as chief technology officer at Aave Labs.

“Aave V3 would not be what it is today without their contributions,” Kulechov said. Delegate Marc Zeller called the move “devastating,” noting that much of the platform’s revenue depends on BGD’s code.

Aave, with more than $26 billion in user deposits, is the largest decentralized finance lending protocol.

Advertisement

It is governed by tokenholders through a DAO structure, but tensions have been building for months over the role of Aave Labs and control of the brand.

Delegates recently sought to transfer brand assets, including naming rights, social media accounts and the aave.com website, from Labs to the DAO, though the proposal narrowly failed.

Labs later offered to redirect revenue from Aave-branded services to the DAO but tied the plan to recognizing Aave v4 as the project’s future technical foundation.

That clause alarmed BGD, which described Aave v3 as the ecosystem’s “crown jewel” and warned that altering lending parameters could pressure users to migrate prematurely.

Advertisement

Aave Labs Says V3 Will Remain Supported With No Immediate Migration

Aave Labs said there is no immediate timeline for migration and that v3 will remain supported. Kulechov added the company can assume maintenance duties if needed, and that the protocol will continue operating normally.

BGD’s contract ends April 1. The firm has offered a short-term transition arrangement to help the DAO find a replacement, marking the first tangible break in what was once viewed as one of DeFi’s most stable governance models.

Meanwhile, the US Securities and Exchange Commission formally concluded its multi-year investigation into the Aave Protocol without recommending any enforcement action.

Advertisement

The action ends nearly four years of regulatory uncertainty surrounding one of decentralized finance’s most widely used lending platforms.

The post Aave’s “Civil War” Claims First Casualty as Key Developer Walks Away appeared first on Cryptonews.

Source link

Advertisement
Continue Reading
Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *

Crypto World

IoTeX Investigates Token Safe Incident as Analysts Estimate $4.3M Loss

Published

on

IoTeX Investigates Token Safe Incident as Analysts Estimate $4.3M Loss

Decentralized identity protocol IoTeX has confirmed that it is investigating unusual activity tied to one of its token safes after onchain analysts flagged a possible security incident.

In a Saturday post on X, the project said its team was “fully engaged, working around the clock to assess and contain the situation.” IoTeX added that early estimates indicate the potential loss is lower than circulating rumors and that it has coordinated with major exchanges and security partners to trace and freeze funds linked to the attacker.

“The situation is under control. We will continue to monitor closely and provide timely updates to the community,” the project said.

IoTeX’s native token (IOTX) dropped following the incident, with the price sliding more than 8% over 24 hours to around $0.0049, according to data from CoinMarketCap.

Advertisement

Related: CertiK links $63M in Tornado Cash deposits to $282M wallet compromise

Analyst says compromised key drained $4.3 million

The response came after onchain investigator Specter claimed a private key connected to the safe may have been compromised.

The onchain sleuth revealed that the wallet was drained of several tokens, including USDC (USDC), USDt (USDT), IoTeX (IOTX) and wrapped Bitcoin (WBTC), with losses estimated at roughly $4.3 million. The stolen funds were reportedly swapped into Ether (ETH), and about 45 ETH was bridged to Bitcoin.

IoTeX wallet breach led to $4.3 million in losses. Source: Specter

The analyst also published addresses associated with the suspected attacker, alongside transaction records showing rapid movements through decentralized exchanges and token swaps. The activity suggested an attempt to convert assets quickly and move them across chains to complicate recovery efforts.

Related: SwapNet exploit drains up to $13.3M from Matcha Meta users

Advertisement

Most crypto projects don’t recover from hacks

As Cointelegraph reported, nearly 80% of crypto projects hit by major hacks struggle to recover, largely due to mismanaged responses rather than the immediate financial damage, according to Web3 security leaders. Immunefi CEO Mitchell Amador said many teams are unprepared for breaches, leading to delayed decisions and poor communication during the crucial early hours, which worsens losses and shakes user confidence.