Kelp DAO Blames LayerZero for Approving $300M Bridge Exploit Setup

Kelp DAO is pushing back against LayerZero's assertion that a vulnerable 1-of-1 verifier configuration caused the $292 million bridge hack on April 18, arguing that LayerZero itself approved and documented the setup as a default option. The dispute marks a critical moment in cross-chain DeFi, where responsibility for bridge security architecture remains unclear.

The liquid restaking protocol claims LayerZero explicitly endorsed the configuration that became the exploit vector. LayerZero, a major player in cross-chain messaging infrastructure, had previously pointed to the 1-of-1 verifier model as the root cause of the attack. A 1-of-1 verifier setup means a single entity controls message validation, creating a critical single point of failure that an attacker can target.

Kelp DAO stated that the 1-of-1 verifier setup at the center of the April 18 exploit was LayerZero's own documented default. The distinction matters enormously. If LayerZero positioned this configuration as a standard, recommended approach, the liability calculus shifts dramatically toward the infrastructure provider. If LayerZero merely offered it as one available option among many, responsibility may rest with Kelp for failing to implement additional safeguards.

The $300 million loss ranks among the largest bridge exploits in crypto history, alongside the Ronin bridge hack (March 2022, $625 million), the Poly Network attack (August 2021, $611 million), and the Nomad bridge exploit (August 2022, $190 million). Each incident exposed configuration weaknesses or validator vulnerabilities that attackers exploited systematically. Bridge exploits have become a recurring pattern in cross-chain DeFi, suggesting that architectural decisions made during deployment often prove catastrophic when deployed at scale.

LayerZero's response will likely hinge on a technical distinction: whether approving a default configuration constitutes an endorsement of it as production-ready without additional security measures, or merely an acknowledgment that the option exists. Industry observers are questioning whether either party adequately stress-tested the bridge before accepting significant total value locked (TVL).

The debate raises uncomfortable questions about responsibility boundaries in DeFi infrastructure. When a protocol provider documents a configuration and another protocol implements it, who bears ultimate liability when that configuration fails? Kelp DAO's counter-narrative suggests LayerZero faces reputational and potentially legal pressure to share accountability. LayerZero could argue that while the 1-of-1 verifier was available as a default, Kelp bore responsibility for implementing additional security layers or migrating to a more robust validator configuration.

The timing of these accusations matters. Bridge hacks typically trigger finger-pointing within hours, but the specificity of Kelp's claims about LayerZero's documentation suggests the team has reviewed communications and technical specifications in detail. If Kelp can produce evidence that LayerZero explicitly approved the setup in writing, that evidence could shift industry perception of who failed whom.

For the broader cross-chain DeFi ecosystem, this dispute underscores a fundamental problem: infrastructure providers and application developers lack clear contracts around security responsibility. LayerZero's protocol powers billions in cross-chain value, making its design choices consequential for dozens of dependent protocols. If LayerZero recommended or approved configurations that later proved exploitable, the incident raises questions about the vetting process for default settings across the entire ecosystem.

Both parties have financial and reputational incentives to deflect blame. Kelp DAO faces pressure from affected users and liquidity providers. LayerZero risks losing trust from protocols that rely on its infrastructure. The resolution of this dispute will likely set a precedent for how other cross-chain DeFi incidents are adjudicated going forward.