
Kelp DAO Blames LayerZero for $292M Bridge Hack, Plans Chainlink Switch
Kelp DAO is accusing LayerZero of responsibility for an April 18 exploit that drained roughly $292 million to $300 million from its liquid restaking bridge, and says it will move to Chainlink's cross-chain infrastructure. The dispute is unfolding alongside a $71 million court fight between the two parties.
Written by CoinArticle’s AI Newsroom · from 2 cited sources. How we work
The Exploit and the Disputed Cause
Kelp DAO attributes an April 18 exploit that drained between $292 million and $300 million to a verifier configuration that, in its account, was LayerZero's own documented default. The figures differ across reporting: Decrypt cites $292 million, while The Defiant reports $300 million, and the gap likely reflects differing methodologies for valuing the stolen assets at the time of the hack.
The core of the dispute is a 1-of-1 verifier setup, meaning a single verifier was able to approve cross-chain messages. Kelp argues this configuration was the default LayerZero documented for its integration, and that responsibility for the default rests with LayerZero. Neither source reports a LayerZero response to that specific claim in the material reviewed here.
Protocol Migration to Chainlink
Kelp has said it plans to switch its cross-chain messaging to Chainlink. Migrating a liquid restaking protocol's bridge is a substantive engineering change, and the timeline and scope of that move are not detailed in the source reporting.
Parallel Litigation
The blame dispute is running alongside a $71 million court fight between Kelp and LayerZero. Because the lawsuit and the public accusations are both in play, neither party's account has yet been tested through a ruling, and claims about fault should be read as contested positions rather than settled findings.
Why It Matters
For Traders
Open positions tied to Kelp-related assets face elevated uncertainty while the litigation and migration remain unresolved.
For Investors
The episode highlights concentration risk in single-verifier bridge configurations, a structural issue that may reshape how restaking protocols evaluate cross-chain vendors.
For Builders
Teams relying on default verifier settings should audit their own threshold configurations, since the dispute turns on whether a 1-of-1 setup was a documented default.
This article is for information only and is not financial advice. Read the full disclaimer.






