Cronje Resurfaces With Unfinished Code, and the Losses Start Again

Andre Cronje could not stay away for long.

Two weeks earlier, he had gone quiet on crypto Twitter after the Eminence scandal put a dent in his reputation as DeFi's favored developer. In the interval, the yield farms that had once minted fortunes dried up, and Blue Kirby, Cronje's in-house daemon project, stopped functioning entirely.

When Cronje re-emerged, he did so with another batch of code he had not finished — and, as before, he insisted it was meant only for testing. That disclaimer did nothing to slow down the crowd rushing to deposit, and the result was another round of what might be called on-chain natural selection playing out live, visible in the transaction history of the contract.

Two separate losses followed, with two different causes. The drain of funds from the EMN contract looked like an accident — an exploit carried out by an unidentified attacker. The LBI token was a different story: its price collapse was set off deliberately, when Cronje edited the Medium post in which the project had originally been announced.

That distinction is part of why many in the community hold Cronje responsible for what happened. Given what had already occurred with EMN, it is reasonable to assume he understood that people would pour money into whatever he released next. It is equally reasonable to assume he could have anticipated what would happen to LBI's price if he attached a stark warning to the announcement after users had already deposited.

Still, the code shipped with disclaimers attached, and anyone who deposited did so aware of the risk — which suggests culpability is shared rather than one-sided.

Cronje had stepped back from Twitter on September 29th specifically to concentrate on building. Many assumed that meant he would return with something polished; instead, he pushed more incomplete code to Ethereum mainnet, and the letdown was palpable. That cycle of public disappointment appears to have soured him — he swung from silence to open mockery once the project fell apart, using Twitter to taunt the users who had lost money.

Judging by his posting history, the account behind this seemed to have rebranded from @andrecronjetech to @andrecronjedev — raising the question of whether crypto Twitter's self-styled "degens" had changed at all, or simply found a new face to rally around.

Update: the @andrecronjedev account turned out to be a troll operation. After this piece went up, the real @andrecronjetech account was used by Cronje to address his role in the DeFi drama directly. Whether the appetite for these live experiments has finally cooled, or degens will simply keep being degens, remains an open question — but the era symbolized by 0xc4ad needs to end, and the community should stop rewarding this kind of recklessness.

Neither side appears to have absorbed the lesson EMN should have taught. Depositors keep behaving recklessly, and Cronje still seems reluctant to accept that his growing profile now comes with an obligation to protect the people who use what he builds.

If, as he described it, the code was only ever "shared for devs to help think tank and figure out how to create a new distribution mechanism," there were quieter ways to share it — anonymously, or with a small circle of collaborators, rather than to the open market.

That said, it is easy to sympathize with the frustration of watching a piece of experimental work get swarmed by opportunists chasing yield rather than engaging with the idea itself. His reaction, however unhelpful, is understandable in that light.

Cronje remains one of the most capable builders in DeFi, and none of this should discourage him from continuing to ship work. Putting unfinished ideas in front of the public is inherently uncomfortable, and the stakes here made it more so than usual.

Twice now, deployments framed as experiments have ended in losses, and yet the crowd keeps showing up hoping for a repeat of the YFI payoff — a reminder that the original YFI outcome may simply have been an exception rather than a pattern.

Ultimately, both the developer and the depositors bear some responsibility, and there is no clean way to assign blame entirely to one side. But no one forced anyone to put money in. Participants understood the risk going in, and they paid the price when it materialized.