Kelp DAO Shifts Blame to LayerZero for $290 Million Disaster, Citing Default Settings

A recent cryptocurrency incident has sparked a heated debate, with Kelp DAO pushing back against LayerZero's assessment of a $290 million exploit. According to a source familiar with the matter, Kelp plans to argue that the compromised verifier was actually part of LayerZero's infrastructure, and that the setup in question was based on LayerZero's default configuration. This development has significant implications for the cryptocurrency community, particularly in the context of cross-chain messaging and security protocols. Kelp, a liquid restaking protocol, utilizes LayerZero's infrastructure to facilitate the transfer of its receipt token, rsETH, between blockchains. The recent exploit, which resulted in the loss of approximately $290 million, has raised questions about the security of these systems and the allocation of responsibility. Kelp claims that the compromised decentralized verifier network (DVN) was part of LayerZero's own infrastructure, rather than a third-party verifier. Furthermore, the source asserts that the setup in question, which has been criticized as a '1/1 configuration,' was actually the default configuration recommended by LayerZero. This configuration, which relies on a single validator to sign off on cross-chain messages, has been implicated in the exploit. In response to these claims, security researchers have expressed skepticism about LayerZero's attempts to shift the blame to Kelp, with some accusing the company of 'deflecting responsibility' for its own compromised infrastructure. As the situation continues to unfold, it remains to be seen how the cryptocurrency community will respond to these developments and what measures will be taken to prevent similar incidents in the future.