$KELP Catalyst Posts
April 20, 2026Single-day social intelligence recap and verified catalyst posts · ← Back to $KELP Profile · Market Rankings
💬 Curated Viral Posts & Community Evidence
95 source posts analyzed· 2026-04-20T05:06:25+00:00The attack was way more sophisticated than I expected and aimed at LayerZero infrastructure taking advantage of KelpDAO laziness.
· 2026-04-20T04:05:12+00:00Live evidence for the @aave x @KelpDAO x @LayerZero_Core governance war room on second-order risk. @avantprotocol is currently running a single $156M sUSDe looping position on Aave Mantle. $140M USDT0 + $20M USDC borrowed against it. Net APY -135% (net of sUSDe embedded yield
· 2026-04-20T11:01:48+00:00we should get layerzero, kelp, aave into a room to figure things out between them. so far things are not looking good, everyone has lawyered up and going full pvp on each other.
· 2026-04-20T01:29:06+00:00Based on nothing but vibes, we’re going see an announcmeng from LayerZero, Aave, and Kelp this week where they share that they’ve found a large investor to backstop the missing funds in return for some guarantee shares of revenue from the protocol until funds are returned.
· 2026-04-20T15:02:13+00:00To be clear: North Korean hackers infiltrated LayerZero Labs’ centralized infrastructure and stole $290M Rather than explain how that happened, LZ put out a statement carefully worded by lawyers to minimize their liability and threw KelpDAO under the bus for trusting them
· 2026-04-20T04:59:24+00:00tldr KelpDAO made the decision to use a 1 of 1 validator for the entire bridge and their 1 got breached. How could this have been avoided?
· 2026-04-20T02:03:23+00:00OneKey Founder Yishi on Handling the KelpDAO Hack 1, Best case: negotiate with the hacker and offer a 10-15% bounty. 2, If talks fail, let the LayerZero ecosystem fund cover most of the loss. 3, KelpDAO is the weakest; compensate with tokens + future revenue, or sell the whole
· 2026-04-20T17:30:10+00:00ngl the config convo feels a bit surface level here what actually happened sits deeper and that’s where this gets uncomfortable for @LayerZero_Core you can’t run the infra, push docs that default to 1/1, see a huge chunk of the ecosystem including @KelpDao follow that path and
· 2026-04-20T00:50:28+00:00KelpDAO dismantled the lock on its own door, LayerZero is selling the kind of door where you can pick the lock yourself, and Aave assumed the neighbor's door was definitely locked tight, so it confidently took the neighbor's key as collateral. The best outcome is to negotiate
· 2026-04-20T14:47:51+00:00There is one path forward for @aave and @KelpDAO 1. Aave teams "liquidates" the rsETH/wETH position, assuming the rsETH tokens and paying the wETH debt. This gets Aave back online and functioning normally. So it can move forward and avoid any further disruption. 2. Kelp will
· 2026-04-20T10:28:31+00:00The Fear and Greed Index is at 53 right now—looks like the market's pretty calm on the surface, but it's actually a bit fragile. Bullish and bearish news are coming one after another, and the market's just swinging back and forth between these two extremes. KelpDAO's
· 2026-04-20T18:01:13+00:00Why is KelpDAO blaming LayerZero? "KelpDAO's leaked memo says it relied on LayerZero's documentation, default configurations, and team guidance when setting up the bridge." "LayerZero is saying KelpDAO should have used a more secure configuration." Andy's take: "That is not
· 2026-04-20T20:55:00+00:00tl;dr the situation is still unresolved, but: - Aave is prepared to use treasury funds (up to $181M) to help plug to hole - Various external parties have made commitments to help - User haircuts will depend on how KelpDAO handles losses: - if socialized across all holders,
· 2026-04-20T14:48:43+00:00This is the tension around rsETH and why everyone is waiting on Kelp. My prediction is lawsuits occur either way, as is typical in creditor-on-creditor violence. The term “equitable subordination” is likely to enter the vocabulary of folks stuck in this, given the hazy status
· 2026-04-20T15:34:53+00:00So let me get this straight. Layerzero blames Kelp. Kelp blames layerzero. Aave is silent. And seems like all 3 are not communicating. I urge all 3 parties to get a grip. If you are all worried about liability so much, inaction also carries liability. The handling of this
· 2026-04-20T20:53:56+00:00KELP rsETH BACKING SCENARIOS FROM LLAMARISK 1. Full socialization • Mainnet and L2s are treated equally • Backing loss: 15.12% • Aave's bad debt: $123,708,727 • Umbrella covers $54,060,000 only of mainnet losses (60%) 2. Losses isolated to L2s • Mainnet retains full value,
· 2026-04-20T03:57:16+00:00AAVE HIT BY $9.5B TVL DROP AFTER $292M COLLATERAL EXPLOIT SHOCK Aave’s total value locked plunged by around $9.5 billion, over the past two days, according to DeFiLlama, following a major exploit involving $rsETH. Attackers used $292 million in stolen rsETH from Kelp’s bridge
· 2026-04-20T05:12:11+00:00From a purely third-party perspective, the responsibility allocation for this incident: LayerZero -45%, responsibility: self-operated DVN was attacked; kelpdao -45%, responsibility: using a single DVN, L0's self-operated DVN; Aave -10%, responsibility: discovering the issue
· 2026-04-20T22:24:43+00:00Tom Kysar explains how the $300M KelpDAO hackers would theoretically offramp their money “I would try to return it for 10% of the value. I don’t know how to get that money out. Once you steal a large amount of money, it’s still really hard to get it out. Today, people try to get
· 2026-04-20T08:32:00+00:00NEW POLYMARKET: Will Kelp DAO socialize the losses from $292 million hack?
· 2026-04-20T18:30:06+00:00>default path → single @LayerZero_Core DVN docs push 1:1 >~40% of apps follow it (including @KelpDao ) >infra gets compromised (RPCs poisoned, failover forced) >multiple protocols pause >worked as intended something really not lining up here @LayerZero_Core pushed this path,
· 2026-04-20T09:19:03+00:00About $740 million was lost to hacks in Q1 2026 alone. This is unbelievable. - Kelp DAO: $292–293 million - Drift Protocol: $285 million - Step Finance: $27–40 million - Truebit: $26–26.4 million - Resolv Labs: $23–25 million - Grinex: $13.7–15 million - SwapNet: $13.4–16.8
· 2026-04-20T15:58:18+00:00LZ blaming Kelp. Kelp blaming LZ. Aave saying their hands are tied. In truth nobody escapes blame. Kelp should have required more DVNs, or rate limits, or both. LZ should have not let their DVN get pwned. Aave should not have onboarded a poorly secured token as collateral.
· 2026-04-20T16:19:47+00:00This seems like some revisionist history. Spark listed rsETH in early 2025. It was frozen for a week about a month later when rsETH supply was being over minted to Kelp’s fee collector. Spark discontinued it not because of explicit safety concerns, but because Abraxas was the
· 2026-04-20T14:35:37+00:00what I assume is going on at kelp is that they would also prefer to blame LZ and claim its a bridge hack, Kelp staking is 1:1 business goes on but they're afraid of Kraken etc just suing their ass wonder if the "interoperable OFT" script implies opting into one net unified pool
· 2026-04-20T13:24:00+00:00LayerZero says the $290M KelpDAO exploit wasn't a protocol failure but a configuration failure Single verifier setup combined with compromised RPC nodes and DDoS induced failover led to a forged cross chain approval This wasn't a smart contract bug it was infrastructure being
· 2026-04-20T17:52:53+00:00AAVE, LayerZero and Kelp when it's time to describe how big their responsibility was:
· 2026-04-20T20:40:15+00:00With the size of the respective treasuries, if they spread evenly then shared the burden among AAVE, L0, Kelp, the L2s they could clear all the bad debt and not even touch umbrella. Imo that'd be the best outcome
· 2026-04-20T15:17:45+00:00This is bad. Kelp's response confirms that it's still currently a blame game b/w Kelp and LayerZero. Kelp is saying 1/1 DVN was LayerZero's default config in their quickstart guide, so they used that. And the infra that got compromised was LayerZero's own RPCs.
· 2026-04-20T09:50:21+00:00GOAT Network Security Advisory Following LayerZero’s post-mortem of the @KelpDAO incident, the @LayerZero_Labs DVN will no longer sign messages for apps using a 1-of-1 DVN configuration. As a result, several cross-chain assets on GOAT Network are temporarily affected and some
· 2026-04-20T15:32:00+00:00KELP DAO MAY BLAME LAYERZERO FOR SATURDAY'S EXPLOIT According to a recent post from Coindesk, Kelp DAO ( @KelpDAO ) is preparing a memo blaming LayerZero ( @LayerZero_Core ) for the $292 Million rsETH exploit. The platform stated it relied on LayerZero's documentation, default
· 2026-04-20T05:22:06+00:00LayerZero says North Korea's Lazarus likely behind Kelp DAO exploit; blames single-point setup
· 2026-04-20T15:33:13+00:003/ The EarnETH team and subvault curators are actively working to deleverage where possible and reduce risk across all strategies. The outcome for the rsETH position is dependent, among other things, on decisions and actions by Kelp, LayerZero, and Aave, specifically how losses
· 2026-04-20T05:26:52+00:00So, it seems that North Korean hackers were also behind the Kelp DAO hack. That's 2 weeks after their $285m Drift hack. The DPRK & political insiders are the only ones making money in crypto right now.
· 2026-04-20T07:03:43+00:00According to LayerZero's statement, KelpDAO was hit by a $290 million attack. Initial findings indicate that the attack points to the North Korea-linked Lazarus Group. It was reported that the issue stemmed from targeting KelpDAO's single-validator-based structure and RPC
· 2026-04-20T09:19:51+00:00One of the benefits of CeFi or semi-CeFi is that when something goes wrong, you know exactly who to hold accountable for recourse—it won't be like AAVE, L0, KelpDAO, where everyone just points fingers at each other. @UnitasLabs If something goes wrong, I'll go after
· 2026-04-20T05:30:33+00:00NEW: LayerZero says North Korea's Lazarus likely responsible for $292M Kelp DAO exploit - @LayerZero_Core explained that attacker poisoned RPC nodes used by DVN, which verifies cross-chain messages. - It blamed @KelpDAO for using 1/1 DVN setup, even after LZ advised against
· 2026-04-20T13:30:00+00:00𝗧𝗵𝗲 $𝟮𝟵𝟯𝗠 𝗞𝗲𝗹𝗽 𝗗𝗔𝗢 𝗘𝘅𝗽𝗹𝗼𝗶𝘁: 𝗪𝗵𝗲𝗻 𝗖𝗼𝗹𝗹𝗮𝘁𝗲𝗿𝗮𝗹 𝗕𝗲𝗰𝗼𝗺𝗲𝘀 𝗖𝗼𝗻𝘁𝗮𝗴𝗶𝗼𝗻 The largest DeFi exploit of 2026 didn't target a single protocol. It targeted the trust that holds composable finance together. 𝗪𝗵𝗮𝘁 𝗛𝗮𝗽𝗽𝗲𝗻𝗲𝗱 –
· 2026-04-20T21:48:50+00:00Eth culture incentivized and encouraged and promoted scam bribe projects like Eigenlayer which created the conditions that allowed 10 figures to be borrowed against Kelp coin
· 2026-04-20T15:51:13+00:00end of the day; no matter who says what it is LayerZero's mistake, they got hacked, hacker was able to find out what backup nodes they used and their IP as well blaming this on Kelp is retarded, but Kelp is also retarded for blindly trusting layerzero
· 2026-04-20T13:34:10+00:00ICYMI: Here's a quick news recap from today's Asia & EMEA sessions @TheBlockCo LayerZero said North Korean hacker group Lazarus is likely responsible for the $292 million Kelp DAO exploit. Strategy acquired an additional 34,164 BTC for approximately $2.54 billion — its
· 2026-04-20T17:58:36+00:00Imagine explaining to your wife that you have material losses because of Kelp DAO
· 2026-04-20T05:32:33+00:00kelp dao guys are retarded man i feel bad for layer zero team. the attack sounds honestly pretty wild but the wildest part is the oapp having a 1/1 config. absolutely inexcusable.
· 2026-04-20T15:10:11+00:00KelpDAO, LayerZero, Aave publishing postmortem’s on this weekends hack.
· 2026-04-20T12:29:59+00:00XION is unaffected by the recent @KelpDAO exploit. Our TVL remains at $0
· 2026-04-20T07:02:55+00:00JUST IN: Aave TVL crashes $8.45 billion in 48 hours as DeFi bleeds over $13 billion across chains. This comes after the $290M+ KelpDAO rsETH exploit triggered panic, liquidity outflows, and forced DeFi deleveraging across major protocols.
· 2026-04-20T04:58:04+00:00This case is not a failure of LayerZero, but a failure to properly understand the trust model. - @LayerZero_Labs allows each application to define who and how many DVNs they trust - @KelpDAO chose the lowest trust diversity with the highest risk: relying on a single source
· 2026-04-20T05:17:50+00:00Crazy how much this is written to distance themselves from blame when it was fundamentally a successful attack on their infrastructure. Yes, the kelp team should’ve multi-DVN’d. But they still lost control over multiple incredibly sensitive parts of their stack and have clear
· 2026-04-20T02:00:01+00:00Kelp DAO lost $292M because one key got leaked. This was preventable by privacy project I researched 11 projects that fix this exact problem 1. MPC / Threshold Signatures Key sharded into pieces. No one holds full key. @LitProtocol : MPC + TSS + TEE @FireblocksHQ :
· 2026-04-20T16:07:12+00:00A $290M Kelp exploit just drove $2B out of YBS in 48 hours. That's the largest outflow in the sector's history, 8% of total supply.
· 2026-04-20T21:30:50+00:00TLDR: @KelpDAO architecture was safe. Attack directly targeted @LayerZero_Core infrastructure and @KelpDAO immediately intervened once they became aware of this.
· 2026-04-20T02:05:02+00:00The KelpDAO / Aave incident isn’t a one-off. It’s a warning shot. Frontier AI models (like Anthropic’s) are about to massively amplify offensive capabilities. They aren't just scanning for bugs anymore—they are reasoning across systems, simulating attack paths, and exploiting
· 2026-04-20T21:10:47+00:00Here's what really happened. Bad defaults shipped by LayerZero, pushing responsibility to integrators. Blaming @KelpDAO is wrong. We need to do better. Sane defaults, secure-by-default, defense-in-depth, decentralization to avoid single points of failure, and better opsec.
· 2026-04-20T12:35:58+00:00we should get layerzero, kelp, aave into a room to figure things out between them. so far things are not looking good, everyone has lawyered up and going full pvp on each other.
· 2026-04-20T16:49:44+00:00seems neither kelp nor layerzero wanna take the blame for the $290m hack this gonna be a fun watch lmao
· 2026-04-20T15:32:20+00:00On Saturday, Kelp DAO's LayerZero bridge was hacked for about $292M. On Sunday, Aave stablecoin net borrow flows got hit for -$763.5M, according to our stablecoin dashboard. Despite not even being hacked, Aave was one of those that got hit the hardest. Here’s why: The attacker
· 2026-04-20T12:32:34+00:00At one point I had 7 figures on KelpDAO farming Eigen Layer. Today, I couldn’t imagine using DeFi, at all, in its current state. On chain finance will look more like FinTech than OG DAO farming. And that’s fine.
· 2026-04-20T17:12:28+00:00Tough day for the ecosystem. Sending strength to the @LayerZero_Core team and the @KelpDAO community- these state-level attacks are getting sharper, and we're all learning in public. This wasn't a protocol bug. It was RPC-layer poisoning + a DDoS to force failover onto
· 2026-04-20T11:36:19+00:00LayerZero Pins $292M KelpDAO Bridge Hack on North Korea’s Lazarus Group
· 2026-04-20T19:50:21+00:00Security on @apyx_fi : time locks, multisigs, daily limits for bridging ... to prevent hacks like Drift, Resolv, Kelp
· 2026-04-20T12:17:52+00:00Layerzero, Aave and Kelp rn
· 2026-04-20T13:18:01+00:00have not heard a peep about layerzero, Kelp, morpho, aave, nothing on LinkedIn about any of this at all
· 2026-04-20T09:00:03+00:00The Liquid Restaking Protocol of Kelp DAO was attacked on 18/04/2026, causing estimated losses of approximately 292 - 294 million USD. Cause: Attackers exploited a security vulnerability in Kelp DAO's cross-chain bridge, which is operated using LayerZero technology. Stolen
· 2026-04-20T09:37:38+00:00PTSD LEVELS RISING FAST $292M exploited from @KelpDAO via @LayerZero_Core . Collateral damage spread to @aave users who can't withdraw their funds. Capital is running out of DeFi as crypto bros realise their funds are NOT SAFU.
· 2026-04-20T01:21:48+00:00The Grotto is not affected by the Kelp DAO situation. Out of an abundance of caution, we've decided to pause any bridges that rely on Layer0 until we have a full understanding of the situation. If you have to move your bobs around, I recommend against it. We are monitoring
· 2026-04-20T16:51:30+00:00KelpDAO vs LayerZero.
· 2026-04-20T22:05:26+00:00Kelp DAO has published their official statement on this incident today. Key points from Kelp's statement ・The attack targeted LayerZero-operated RPC nodes (2 nodes compromised + DDoS on a 3rd) ・Kelp's own systems were not involved in building or operating that
· 2026-04-20T15:22:51+00:00$292M stolen from KelpDAO in 46 minutes. No smart contract bug. No private key leak. Every on-chain check passed cleanly. The attacker broke the verification layer not the code. Here's exactly how it happened
· 2026-04-20T05:35:20+00:00whale accumulation is solid, jupiter partnership adds legitimacy. but solana ecosystem has major liquidity stress right now from the kelpDAO fallout. kamino pools at 100% utilization. watch how fast solana fixes its liquidity issues. that's your next leg indicator.
· 2026-04-20T15:38:40+00:00Rumors that Kelp DAO is preparing a memo blaming LayerZero for Saturday's $292 million rsETH exploit, saying it relied on LayerZero's documentation, default configurations and team guidance when setting up the bridge. Here we go… this is about to get interesting.
· 2026-04-20T20:36:56+00:00Regardless who you blame for the recent DeFi exploit, both @aave and @LayerZero_Core have released long-form statements delving into the rsETH situation. It looks very poor that's its been over 48 hours and it's mostly silence from @KelpDAO .
· 2026-04-20T04:33:47+00:00Dowtrend with hackers running rampant Just the beginning of the month, @DriftProtocol got hacked for $285M, and yesterday it was @KelpDAO 's turn to get hacked for $293M The hacker has brazenly drained 116,500 rsETH from Kelp DAO's cross-chain bridge running on LayerZero.
· 2026-04-20T21:20:37+00:00Built RPC Watch. KelpDAO got me wondering how many projects run on a single RPC. Answer: 900. One outage and the chain goes dark. One compromise and every user gets fed lies. rpc-watch.vercel.app
· 2026-04-20T17:34:51+00:00Withdrawals are paused to ensure fair treatment of all depositors. Lido's first-loss protection mechanism applies on EarnETH depositors. Final impact depends on actions by Kelp, LayerZero, and Aave governance. Mellow is coordinating directly with all relevant parties.
· 2026-04-20T23:24:33+00:00This is my interview with a Cyperpunk. He's assembling an army of hackers to restore order. We talk about @CantonNetwork , @KelpDAO , privacy, security, accountability, anarcho-capitalism, and the fundamental flaws of universally open infra. Enjoy. @CantonFdn $cc
· 2026-04-20T04:30:17+00:00Trust between Kelp’s bridge & Aave
· 2026-04-20T16:52:49+00:00the real stress test is internal, not iran watch aave liquidity crunch cascading through ethena positions. $268m stuck on mantle, negative apys on loopers. layerzero pauses across 15+ protocols after kelp exploit spark absorbing the outflow. sky ecosystem with 8yr no exploit
· 2026-04-20T01:51:38+00:00looking like they had all their money tied up in kelp dao
· 2026-04-20T23:33:05+00:00LAZARUS IS BACK: KELP-AAVE CONTAGION AND DEFI IN PANIC
· 2026-04-20T09:38:52+00:00different animal. kelp dao was a bridge config disaster (1-of-1 layerzero setup), not a staking protocol exploit. stETH's core mechanism wasn't touched. lido even helped build the aWETH redemption fix for the fallout.
· 2026-04-20T09:07:12+00:001/11 The @KelpDAO hack wasn’t just another exploit. It exposed something deeper: in DeFi, the weakest layer isn’t always the contract… it’s the assumptions between systems. A thread
· 2026-04-20T23:43:10+00:00Kelp DAO Points to LayerZero as Responsible for the rsETH Exploit Nearly USD $290 million was drained from the Kelp bridge. Kelp argues that the failure was in LayerZero's infrastructure and default configurations. The incident has raised concerns about security in
· 2026-04-20T23:20:10+00:00Read the Layerzero and Kelp DAO post mortem articles and all I can see to it is that nobody is ready to take the blame for the hack that happened, lmao. Kelp Dao is pointing fingers to L0 and L0 is pointing fingers back to Kelp Dao. Crazy stuffs.
· 2026-04-20T21:40:08+00:00Who decides which users get sacrificed? 17% of rsETH is unbacked. Contracts paused. No redemptions. Kelp DAO has 2 ugly choices: 1) Socialize the 20% loss across all holders 2) Dump 100% of the pain onto L2 rsETH holders only. Who holds the power to pick the losers?
· 2026-04-20T11:19:15+00:00who is they? Layerzero? So there is a war room with only aave + kelp and not layerzero?
· 2026-04-20T19:28:33+00:00Why did the $293M Kelp DAO exploit trigger a DeFi crisis? Find out the answer by Ask Heurist
· 2026-04-20T22:18:23+00:00KelpDAO and LayerZero now doing a finger pointing contest while users lost money, sad
· 2026-04-20T08:34:51+00:00$280M KelpDAO Hack, Who To Blame? The rsETH bridge exploit looks less like a smart contract failure and more like a decentralization failure. If one compromised @LayerZero_Core DVN node was enough to push a fake message through, then calling this a “Decentralized Verifier
· 2026-04-20T19:46:18+00:00Security is back in the spotlight. David Schwartz has flagged potential risks in using DeFi bridge infrastructure for RLUSD, drawing parallels to recent exploits like KelpDAO. For Ripple, this underscores a critical challenge pushing innovation forward while maintaining strong
· 2026-04-20T18:18:23+00:00Following the rsETH/KelpDAO/LayerZero incident, the market has finally begun to properly assess the risk in @aave . Previously, the yields there made it seem as though the risk was practically zero. Now the APY is higher - because keeping money in a lending protocol with a host
· 2026-04-20T05:57:13+00:00This reads that we are not responsible for anything. It was Kelp's fault all along, and we warned them. #Aave #KelpDAO #DeFi
· 2026-04-20T10:06:07+00:00GM CT - KelpDAO $292M gone - Drift $285M gone - RaveDAO insider dump exposed - Aave pools locked at 100% utilization and it's only April stay safe out there
· 2026-04-20T16:33:02+00:00When a bridge breaks, the entire ecosystem trembles. The @LayerZero_Core exploit that hit @KelpDAO ($292M lost) reminds us that security is not optional. The Kelp DAO hack and how Yellow Network redefines security in DeFi On April 18, 2026, @KelpDAO suffered the biggest
· 2026-04-20T23:46:00+00:00the $292M kelp hack was not a code exploit. the $285M drift hack was not a code exploit. both were operational security failures. we have world-class auditors reviewing the locks while nobody checks who has the keys.
· 2026-04-20T20:16:31+00:00@KelpDAO stronger after this, bullish