News listTraders don’t see Kelp socializing losses after $292 million exploit
CoinDesk2026-04-22 08:25:50

Traders don’t see Kelp socializing losses after $292 million exploit

AI Impact AnalysisGrok analyzing...
📄Full Article· Automatically extracted by trafilatura3432 words
Traders don’t see Kelp socializing losses after $292 million exploit Polymarket prices low odds of a system-wide redistribution, as the protocol weighs how to handle an undercollateralized rsETH supply What to know: - A Polymarket contract suggests only a 14% chance that Kelp DAO will spread the losses from the $292 million rsETH exploit across all holders. - The hack drained about 116,500 rsETH from a LayerZero-powered bridge spanning more than 20 blockchains, leaving some rsETH undercollateralized and certain users effectively holding partially unbacked tokens. - Implementing a system-wide loss redistribution, similar to Bitfinex’s 2016 hack response or derivatives exchanges’ auto-deleveraging, would be technically complex and politically fraught. A Polymarket contract on whether Kelp DAO will spread the losses from the weekend's $292 million exploit beyond those directly affected is pointing to a clear answer: probably not. Bettors are giving a 14% chance that Kelp will "socialize the losses," or implement a mechanism forcing rsETH holders on Ethereum, which wasn't hit, to share the pain of users on other chains. The attackers drained roughly 116,500 rsETH from a LayerZero-powered bridge that held the reserves backing the token across more than 20 blockchains. That left parts of the system undercollateralized, with some holders effectively owning tokens no longer fully backed by ether (ETH). “Socializing the losses” would mean Kelp redistributes the shortfall across all rsETH holders, including those on the Ethereum mainnet, rather than leaving losses concentrated among users and protocols tied to the compromised bridge. The most widely cited precedent of this approach came in 2016, when Bitfinex imposed losses on all users after a $60 million hack, effectively mutualizing the hit to avoid shutting down. More recently, derivatives exchanges have used variations of the concept through auto-deleveraging (ADL), in which profitable positions are forcibly reduced to cover losses when insurance funds are exhausted. During the October flash crash, ADL mechanisms were triggered across some venues, closing out even market-neutral positions and leaving traders exposed. These moves are rare and controversial, but they have been used as a last resort to stabilize systems under stress. Kelp’s situation is more complex. The exploit drained the reserve backing rsETH across more than 20 chains, leaving losses fragmented across different user groups and platforms. Holders on affected networks face impaired backing, while others remain relatively insulated. Any attempt to equalize losses would require coordination across chains, clear accounting of liabilities, and a willingness to impose losses on users who may not see themselves as affected. That makes a clean, system-wide redistribution both technically and politically difficult, which may explain why Polymarket traders are approaching the question with skepticism. More For You True Market Mean and Short-Term Holder cost basis form a critical $78.2K to $79.2K range that could define the next major move. What to know: - The True Market Mean, currently around $78,200, represents the average cost basis of actively traded coins and is acting as immediate resistance. - The Short-Term Holder cost basis, near $79,200, reflects the average entry price of recent buyers, who remain underwater and could add to sell pressure if the level is...
Data Status✓ Full text extractedRead Original (CoinDesk)
🔍Historical Similar Events· Keyword + Asset Matching6 items
💡 Currently matching via keywords + symbols (MVP) · Will be upgraded to embedding semantic search later
Raw Information
ID:b0128f1115
Source:CoinDesk
Published:2026-04-22 08:25:50
Category:General · Export Category neutral
Symbols:Unspecified
Community Votes:+0 /0 · ⭐ 0 Important · 💬 0 Comments