Kelp don restart bridging rsETH through LayerZero OFT adapter for Ethereum

Aave don move di first 25,000 rsETH tranche enter LayerZero OFT adapter for Ethereum mainnet on May 13, formally restart rsETH bridging after di LayerZero exploit on April 18 wey drain about $292M in unbacked tokens. Kelp talk say rsETH contracts go unpause withdrawals inside 24 hours once di tranche reach di Ethereum adapter. Deposits and exchange-rate updates dey expected inside 48 hours, and staking rewards wey pause during di incident go dey credited to all rsETH holders. Security measures self don upgrade: LayerZero verification increase from 1 to 4 independent attestors, block confirmation thresholds rise from 42 to 64, L2-to-L2 routes dem deprecated, and Kelp dey migrate infrastructure toward Chainlink CCIP. Di post-mortem attribute di breach to RPC poisoning attack wey link to Lazarus Group’s TraderTraitor unit. For di next two weeks, remaining Aave Recovery Guardian and Kelp recovery tranches go staged into di adapter, targeting up to 117,132 rsETH. Recovered attacker funds (30,765 ETH) still dey for Aave-controlled wallet waiting authorization. For traders, di rsETH bridging restart suppose reduce near-term liquidity and redemption uncertainty for holders, but broader bridge-risk concerns fit make sentiment remain cautious.
Neutral
Di restart straight improve how rsETH bridge dey work by reopening withdrawals and make legitimate collateral flow back enter LayerZero lockbox again. That fit reduce redemption and liquidity stress for rsETH holders for short term. But news still full of one big bridge exploit plus long set of governance/authorization steps (e.g., remaining tranches scheduled over two weeks, attacker funds still pending). Even with hardening (more attestors, higher confirmations, route deprecation, CCIP migration), traders fit still price in lingering bridge risk and headline-driven volatility. Net effect for rsETH-related price likely mixed: good for functionality and confidence, but capped by ongoing security overhang and execution risk.