KelpDAO rsETH Bridge
KelpDAO operated an rsETH cross-chain bridge built on LayerZero messaging. On April 18, 2026, poisoned RPC responses caused the sole LayerZero Labs DVN configured for the affected OApp to attest to a forged Unichain-to-Ethereum message, releasing 116,500 rsETH on Ethereum without a corresponding source-chain burn. KelpDAO paused rsETH contracts across mainnet and several L2s while the incident was investigated.
Bridge facts
- Canonical name
- KelpDAO rsETH Bridge
- Type
- Asset Bridge
- Status
- Paused
- Confidence
- High
- Primary chains
- Unknown, Ethereum
- Primary assets
- Unknown
- Operator
- KelpDAO
- Ecosystem
- KelpDAO
- Launch date
- Unknown
- End date
- Unknown
- Terminal reason
- Not applicable / unknown
- Last reviewed
- 2026-09-09
- Last verified
- 2026-09-09
Incident cases
KelpDAO 2026 rsETH bridge RPC/DVN compromise2026-04-18
On April 18, 2026, attackers compromised LayerZero Labs internal RPC infrastructure and simultaneously disrupted an external RPC path. Poisoned RPC responses caused the sole LayerZero Labs DVN configured for KelpDAO’s rsETH OApp to attest to a forged cross-chain message. With a 1-of-1 DVN configuration, the destination accepted that attestation and released 116,500 rsETH on Ethereum even though no corresponding burn occurred on Unichain.
Evidence records
- KelpDAO Incident StatementLayerZero Labs · Tier 1 · 2026-04-19
- Kelp DAO’s rsETH bridge apparently exploited for roughly $292 million in LayerZero-based attackThe Block · Tier 1 · 2026-04-18
- LayerZero Labs KelpDAO Incident ReportLayerZero Labs · Tier 1 · 2026-05-20
- KelpDAO Incident StatementLayerZero Labs · Tier 1 · 2026-04-19
Official URL status
Official URL recorded as live_verified: https://layerzero.network/blog/layerzero-labs-kelpdao-incident-reportHelp maintain bridge history
Support incident linkage, lifecycle updates, evidence preservation, broken-link replacement, and corrections.
Report a correction
Report missing evidence, incorrect dates, outcome changes, recovery details, reimbursement status, or broken links. GitHub Issues are preferred for structured review; the Google Form is available if you do not use GitHub.