Oscar Wilde’s Guide to DeFi Disasters: “Did Something Change?”

by

In a recent tweet, Ripple CTO Emeritus David Schwartz, with the subtlety of a guillotine, questions the explanation behind the recent KelpDAO exploit-a debacle so spectacular it could only have been orchestrated by a committee of sleep-deprived accountants.

On April 18, KelpDAO, a liquid restaking protocol, suffered a major exploit, losing over $290 million. In an update shortly after, LayerZero stated that the KelpDAO incident was isolated to its rsETH configuration, directly resulting from its single-DVN setup. LayerZero noted that the subject of the highly sophisticated attack was the poisoning of the downstream RPC infrastructure used by the LayerZero Labs DVN-a feat as impressive as a parrot reciting Shakespeare while balancing on a unicycle.

A week after the incident, the crypto community continues to seek answers about what transpired in what is referred to as the biggest DeFi hack to date in 2026. One might wonder if the hackers celebrated with a champagne toast or simply shrugged and moved on to the next vulnerable protocol.

HOT Stories

Shiba Inu (SHIB): Everything Is Clear Now, Bitcoin‘s (BTC) Real Resistance Is $82,000, Another Dogecoin (DOGE) Zero Removal: Crypto Market Review

‘The O.C.’ Star Lambasts Bitcoin on American TV

In this light, Ripple CTO emeritus David Schwartz, with the subtlety of a brick through a stained-glass window, referred to an X reply by LayerZero CEO Bryan Pellegrino in December 2024, where he stated that none of the protocol’s volume relied solely on its Decentralized Verifier Network (DVN). A statement so bold it could only be true if one assumes gravity is optional.

“What percentage of LZ volume relies solely on LZ DVN? The answer to that is 0%. There isn’t a single application setup that solely uses the LZ DVN,” Pellegrino said at the time. A declaration so confident it could only be true if “0%” were a philosophical stance rather than a mathematical one.

Did something change?

In response, Schwartz questions whether something has changed between late 2024 and now. This begs the question: if no application previously relied solely on a single DVN, how could that same configuration now be said to be the root cause of the KelpDAO exploit? A riddle wrapped in an enigma, served with a side of existential dread.

Did something change between December of 2024 and now? Because unless I’m confused, this is saying that the attack on KelpDAO could not have happened as LayerZero described it.

– David ‘JoelKatz’ Schwartz (@JoelKatz) April 25, 2026

“Did something change between December of 2024 and now? Because unless I’m confused, this is saying that the attack on KelpDAO could not have happened as LayerZero described it,” Schwartz questioned. A query as incisive as a spoon to the eye, delivered with the elegance of a poorly timed joke.

If KelpDAO did in fact operate with a single-DVN configuration, it raises questions about whether the system architecture changed after LayerZero’s CEO’s comments in 2024 or whether the earlier claims were not accurate. A mystery as compelling as a blockchain transaction fee.

Along these lines, Ripple’s head of research Aanchal Malhotra, in a recent tweet, shared a few thoughts on the rsETH hack, noting that “the industry is moving toward better primitives-ZK proving, tighter audit standards. But primitives alone aren’t enough. Until security proofs and deployment environments are evaluated together, the gap remains.” A sentiment as profound as a wet blanket at a bonfire, delivered with the urgency of a man who just realized he’s wearing socks with sandals.

Read More

2026-04-25 13:32