


David
4.7K posts

@David_W_Watt
Investor. KOL #Binance & @LBank_Exchange COY 2024 $ETH $INJ $BNB $XRP |CMC : @Davidweb3 |DM open : @DAVID1_web3






The world is showing up for April 28. 4,200+ registered. @Cointelegraph streaming live. @khaleejtimes writing about it. @careem driving people there. Dubai is ready. Are you? 📍 Sky Bubble, The Meydan Hotel Grab your seat 🔗 summit.zigchain.com/2026

Aave service providers and ecosystem partners have established a recovery fund that factors in pending DAO votes, including the Arbitrum governance vote, indicative agreements, and successful execution to restore rsETH’s full backing. We are DeFi United, and resolving this for affected users and the broader DeFi ecosystem is our top priority. We have aligned with @KelpDAO and @LayerZero_Core on the technical steps required to execute our plan. That work is now moving forward. Thank you to everyone who contributed to DeFi United and to the thousands of community members who stood with us throughout. Watching the DeFi community come together has been genuinely inspiring. The final recovery plan, steps for users, and further updates will follow shortly.












UAE SME private credit is moving onchain. $250B in unmet financing demand. A decade of DFSA-regulated operations. Institutional-grade infrastructure. ZIGChain × Beehive. The infrastructure is ready.



UAE SME private credit is moving onchain. $250B in unmet financing demand. A decade of DFSA-regulated operations. Institutional-grade infrastructure. ZIGChain × Beehive. The infrastructure is ready.


layerzero attack was not rpc poisoning in networking poisoning is when the attacker outside the trust boundary taints a shared lookup (dns, arp, cache). the consumer has no reason to distrust the source. this was not that. the attackers got inside layerzero's trust boundary. they accessed the rpc list, compromised two nodes the dvn depended on, and swapped the op-geth binaries. that's an infra breach within the perimeter. supply-chain shaped, not network shaped. and the payload was surgical. the malicious binary cloaked by ip, served forged payload only to the dvn, told the truth to scan and every other caller, then self-destructed to wipe logs and binaries. rpc poisoning makes it sound like something that happened to the infra from the outside. the real story is a targeted implant operating inside the trust boundary. that's a meaningfully scarier attack than the label suggests.
