![Crypto_Goblinz's tweet photo. The KelpDAO exploit (~$290M, is NOT a LayerZero protocol bug. It's a configuration issue and a case study every project with a cross-chain token needs to look at today.
KelpDAO shipped their rsETH OFT with a 1/1 DVN security stack. One required verifier. Zero optional. Threshold 0. Straight from LayerZero Scan's ReceiverOAppConfig on the rsETH bridge pathway:
• requiredDVNCount: 1
• requiredDVNNames: [LayerZero Labs]
• optionalDVNCount: 0
• optionalDVNThreshold: 0
Source and Destination OApp both labeled "Kelp DAO." Destination is the rsETH OFT Adapter on Ethereum: 0x85d456B2DfF1fd8245387C0BfB64Dfb700e98Ef3.
How the attack worked: the forged message's source packet was never actually emitted on the source chain (Unichain). The single required DVN signed an attestation for something that didn't exist and because it was the ONLY required DVN, there was no independent verifier to contradict it. Everything downstream then executed exactly as designed: commitVerification → lzReceive → peer check → OFT decode → rsETH mint. The contracts weren't broken. The verification layer was. One signature and 116,500 rsETH materialized out of thin air on Ethereum.
To be clear: LayerZero V2 is modular by design. Apps pick their own security stack X-of-Y-of-N, multiple independent DVNs, thresholds, block confirmations. No one is forced into any configuration. The protocol gave projects the full toolkit. KelpDAO chose 1/1.
Even reputable DVNs can have a bad day key compromise, infra failure, bad actor, whatever. That's exactly why you want multiple independent verifiers. Redundancy is the whole point. A 1/1 DVN is the cross-chain equivalent of a 1-of-1 multisig on a treasury.
Baseline for any OFT/OApp with serious TVL:
• Multiple required DVNs (3–4+)
• Independent providers (don't stack correlated risk) use canary DVN as it’s also its own independent client.
• Optional DVNs + threshold on top
• Sane block confirmations
If you're a founder or dev with an OFT live in production, pull your Send/Receive ULN config today. Call getConfig() on the endpoint. If requiredDVNCount is 1 and optionalDVNCount is 0, reconfigure before the market does it for you.
Anyone can verify any OApp's config on https://t.co/ovbUskeFCC right now.
Security is the application's responsibility. LayerZero hands every project a powerful, modular security stack it's on the project to actually use it. Kelp's full RCA is still coming, but the root enabler is already onchain and visible to anyone who looks.
Check your configs. Stay safe out there.](https://pbs.twimg.com/media/HGOHJnbWUAAvHji.jpg)
![Crypto_Goblinz's tweet photo. The KelpDAO exploit (~$290M, is NOT a LayerZero protocol bug. It's a configuration issue and a case study every project with a cross-chain token needs to look at today.
KelpDAO shipped their rsETH OFT with a 1/1 DVN security stack. One required verifier. Zero optional. Threshold 0. Straight from LayerZero Scan's ReceiverOAppConfig on the rsETH bridge pathway:
• requiredDVNCount: 1
• requiredDVNNames: [LayerZero Labs]
• optionalDVNCount: 0
• optionalDVNThreshold: 0
Source and Destination OApp both labeled "Kelp DAO." Destination is the rsETH OFT Adapter on Ethereum: 0x85d456B2DfF1fd8245387C0BfB64Dfb700e98Ef3.
How the attack worked: the forged message's source packet was never actually emitted on the source chain (Unichain). The single required DVN signed an attestation for something that didn't exist and because it was the ONLY required DVN, there was no independent verifier to contradict it. Everything downstream then executed exactly as designed: commitVerification → lzReceive → peer check → OFT decode → rsETH mint. The contracts weren't broken. The verification layer was. One signature and 116,500 rsETH materialized out of thin air on Ethereum.
To be clear: LayerZero V2 is modular by design. Apps pick their own security stack X-of-Y-of-N, multiple independent DVNs, thresholds, block confirmations. No one is forced into any configuration. The protocol gave projects the full toolkit. KelpDAO chose 1/1.
Even reputable DVNs can have a bad day key compromise, infra failure, bad actor, whatever. That's exactly why you want multiple independent verifiers. Redundancy is the whole point. A 1/1 DVN is the cross-chain equivalent of a 1-of-1 multisig on a treasury.
Baseline for any OFT/OApp with serious TVL:
• Multiple required DVNs (3–4+)
• Independent providers (don't stack correlated risk) use canary DVN as it’s also its own independent client.
• Optional DVNs + threshold on top
• Sane block confirmations
If you're a founder or dev with an OFT live in production, pull your Send/Receive ULN config today. Call getConfig() on the endpoint. If requiredDVNCount is 1 and optionalDVNCount is 0, reconfigure before the market does it for you.
Anyone can verify any OApp's config on https://t.co/ovbUskeFCC right now.
Security is the application's responsibility. LayerZero hands every project a powerful, modular security stack it's on the project to actually use it. Kelp's full RCA is still coming, but the root enabler is already onchain and visible to anyone who looks.
Check your configs. Stay safe out there.](https://pbs.twimg.com/media/HGOHJnVW4AAIAXN.jpg)
Olivia
Online
Vera
@digitalvera1129
Former PancakeSwap community lead | Builder for more humanity world| Freedom and love
Joined June 2017
238 Following
38 Followers
70 Posts
The risk/reward of putting your capital in crypto has never looked worse.
Not only are returns getting compressed, but AI is massively increasing the attack surface for hacks.
Crypto is no longer the best place on the internet to achieve financial freedom.
If you are still not trading on tradexyz at this point, you probably hate money
The KelpDAO exploit (~$290M, is NOT a LayerZero protocol bug. It's a configuration issue and a case study every project with a cross-chain token needs to look at today.
KelpDAO shipped their rsETH OFT with a 1/1 DVN security stack. One required verifier. Zero optional. Threshold 0. Straight from LayerZero Scan's ReceiverOAppConfig on the rsETH bridge pathway:
• requiredDVNCount: 1
• requiredDVNNames: [LayerZero Labs]
• optionalDVNCount: 0
• optionalDVNThreshold: 0
Source and Destination OApp both labeled "Kelp DAO." Destination is the rsETH OFT Adapter on Ethereum: 0x85d456B2DfF1fd8245387C0BfB64Dfb700e98Ef3.
How the attack worked: the forged message's source packet was never actually emitted on the source chain (Unichain). The single required DVN signed an attestation for something that didn't exist and because it was the ONLY required DVN, there was no independent verifier to contradict it. Everything downstream then executed exactly as designed: commitVerification → lzReceive → peer check → OFT decode → rsETH mint. The contracts weren't broken. The verification layer was. One signature and 116,500 rsETH materialized out of thin air on Ethereum.
To be clear: LayerZero V2 is modular by design. Apps pick their own security stack X-of-Y-of-N, multiple independent DVNs, thresholds, block confirmations. No one is forced into any configuration. The protocol gave projects the full toolkit. KelpDAO chose 1/1.
Even reputable DVNs can have a bad day key compromise, infra failure, bad actor, whatever. That's exactly why you want multiple independent verifiers. Redundancy is the whole point. A 1/1 DVN is the cross-chain equivalent of a 1-of-1 multisig on a treasury.
Baseline for any OFT/OApp with serious TVL:
• Multiple required DVNs (3–4+)
• Independent providers (don't stack correlated risk) use canary DVN as it’s also its own independent client.
• Optional DVNs + threshold on top
• Sane block confirmations
If you're a founder or dev with an OFT live in production, pull your Send/Receive ULN config today. Call getConfig() on the endpoint. If requiredDVNCount is 1 and optionalDVNCount is 0, reconfigure before the market does it for you.
Anyone can verify any OApp's config on https://t.co/ovbUskeFCC right now.
Security is the application's responsibility. LayerZero hands every project a powerful, modular security stack it's on the project to actually use it. Kelp's full RCA is still coming, but the root enabler is already onchain and visible to anyone who looks.
Check your configs. Stay safe out there.
![Crypto_Goblinz's tweet photo. The KelpDAO exploit (~$290M, is NOT a LayerZero protocol bug. It's a configuration issue and a case study every project with a cross-chain token needs to look at today.
KelpDAO shipped their rsETH OFT with a 1/1 DVN security stack. One required verifier. Zero optional. Threshold 0. Straight from LayerZero Scan's ReceiverOAppConfig on the rsETH bridge pathway:
• requiredDVNCount: 1
• requiredDVNNames: [LayerZero Labs]
• optionalDVNCount: 0
• optionalDVNThreshold: 0
Source and Destination OApp both labeled "Kelp DAO." Destination is the rsETH OFT Adapter on Ethereum: 0x85d456B2DfF1fd8245387C0BfB64Dfb700e98Ef3.
How the attack worked: the forged message's source packet was never actually emitted on the source chain (Unichain). The single required DVN signed an attestation for something that didn't exist and because it was the ONLY required DVN, there was no independent verifier to contradict it. Everything downstream then executed exactly as designed: commitVerification → lzReceive → peer check → OFT decode → rsETH mint. The contracts weren't broken. The verification layer was. One signature and 116,500 rsETH materialized out of thin air on Ethereum.
To be clear: LayerZero V2 is modular by design. Apps pick their own security stack X-of-Y-of-N, multiple independent DVNs, thresholds, block confirmations. No one is forced into any configuration. The protocol gave projects the full toolkit. KelpDAO chose 1/1.
Even reputable DVNs can have a bad day key compromise, infra failure, bad actor, whatever. That's exactly why you want multiple independent verifiers. Redundancy is the whole point. A 1/1 DVN is the cross-chain equivalent of a 1-of-1 multisig on a treasury.
Baseline for any OFT/OApp with serious TVL:
• Multiple required DVNs (3–4+)
• Independent providers (don't stack correlated risk) use canary DVN as it’s also its own independent client.
• Optional DVNs + threshold on top
• Sane block confirmations
If you're a founder or dev with an OFT live in production, pull your Send/Receive ULN config today. Call getConfig() on the endpoint. If requiredDVNCount is 1 and optionalDVNCount is 0, reconfigure before the market does it for you.
Anyone can verify any OApp's config on https://t.co/ovbUskeFCC right now.
Security is the application's responsibility. LayerZero hands every project a powerful, modular security stack it's on the project to actually use it. Kelp's full RCA is still coming, but the root enabler is already onchain and visible to anyone who looks.
Check your configs. Stay safe out there.](https://pbs.twimg.com/media/HGOHJn3bwAA03r1.jpg)
Have worked with one of my favorite mods for 4 years and first time to meet in real life 😀community is more important than everything else for community members care and help each other to create! Love the real and inspiring conversation we had with each other . Building !
Who to follow
Concha 
@conchaxhill
Made it, lost it, farming it back.
Bobchris
@Bobchris114
cryptocurrency is like a disco no matter how it changes you have to keep dancing, always Dream big and hustle harder💵🎯
𝒵𝒴𝒩𝒯𝐻𝒪𝑅
@ZeetaCripto
Business Developer | KOL | Community Manager. Building the future of Web3. 🇦🇷 #Bitcoin #Ethereum #Crypto #Web3
In Chinese we say “初心”
Tether froze 3.29M USDT to the hackers.
Tether cares.
当老虎机胜率大于 50% 的时候，就变成了印钞机。Vibe coding 也是一样的道理
Just read 20% of the Q4 U.S . GDP went to AI…
Software eats the world. AI eats software. 😂
Web 4.0 is coming with AI and Crypto work together! A radical changing year is coming !
Full essay: https://t.co/qdrxRkBRuT
We're at an inflection point.
The internet is evolving from moving information to moving value.
Blockchain, stablecoins, and AI aren't separate trends — they're converging into something much bigger: a reimagined global economic system, built natively on the internet.
We are entering a world where, in my view, tens or even hundreds of billions of AI agents will interact and perform economic functions over the internet.
They'll need programmable digital dollars and open infrastructure to do it. That's exactly what we've been building at Circle.
Circle’s Q4 showed this isn't just a vision anymore — it's happening. USDC expansion continued, our share of stablecoin transaction volume approached 50%, and our broader platform expanded well beyond issuance into the infrastructure layer of onchain finance. Arc. CCTP. Circle Payments Network. StableFX. Each one a building block for what comes next.
The opportunity ahead has never been greater. And we're just getting started.
Full results at https://t.co/kG1VoCbj8F
Agents + Robots + USDC = a glimpse of the near future as the machine intelligence economy explodes
Happy Red Horse Year!
🥞 币马奔腾，财源滚滚！
和我们的华语社区一起迎新年，在 PancakeSwap 迎接第一笔好运 👇
参与方式：
• 关注 @PancakeSwapzh & @trustwalletzh
• 点赞 + 转发本推文，并 @ 1 位好友
• 评论区留言：「币马奔腾」 或留下你的新年祝福
奖励：
🎁 总奖池 $200
👥 随机抽取10 位中奖幸运儿
📅 时间：2.13 – 2.23
欢迎申请！
全球大使计划现已启动！
诚邀所有活跃的创作者、建设者及社区领袖，与我们建立正式合作，在拓展影响力的同时获取丰厚回报。
专属福利
✅ 每周瓜分2000积分，创作内容并参与社区互动
✅ 获得官方认证，成为值得信赖的大使
✅ 享受资源支持：流量放大、资源共享
✅ 按贡献等级解锁专属奖励
付出即收获。
寻找志同道合的伙伴，一起建设 Probable ！
I heard that Kimi helps to save money 🤔
https://t.co/bJlfmbuaWD
We're also releasing the original exam for anyone to try.
Given enough time, humans still outperform current models—the fastest human solution we've received still remains well beyond what Claude has achieved even with extensive test-time compute.
Which one you like to use more? USDC or USDT?
在 PancakeSwap 上，收益更高，真正 Based 🟦
本周焦点：PancakeSwap 上的 Base Farms
这些池子的 APR 高于其他平台
ZEN-WETH 🧘 — https://t.co/K2NWGvKcX6
VIRTUAL-WETH 🟩 — https://t.co/ygYJgE3GEy
SOL-USDC 💜💜 — https://t.co/tmAYrsr5KN
WETH-USDT 😇 — https://t.co/A4H10XZp9s
USDC/USDT 🔵🆃 — https://t.co/lzJWw2NB2H
注：这些池子的激励将根据 TVL 进行动态调整，以支持 PancakeSwap 上的 APR。
Happiness comes from the sincere of your heart, not from the ego. It is too real to tolerate any fakeness.
Whoever said “money can’t buy happiness” really knew what they were talking about 😔
Humanity exists all the world, people don’t hate rich guy, they hate capitalists that prioritize money to real human life！
If Jeff Bezos could afford to spend $75 million on the Melania movie & $500 million for a yacht to sail off to his $55 million wedding to give his wife a $5 million ring, please don't tell me he needed to fire one-third of the Washington Post staff.
Democracy dies in oligarchy.
May everyone in 2026 not worship power, not blindly believe in money, and not crave vanity. Spend more time in the sun to replenish your vitality. After all, the greatest light we can feel comes from conscience and sunshine.
MELINDA GATES: “It brings back memories of some very painful times in my marriage — They need to answer to those things, not me.”
She implies she left her marriage and the Gates Foundation for reasons related to Bill’s ties to Epstein.
Last Seen Users on Sotwe
Most Popular Users
Elon Musk
@elonmusk
241M followers
Barack Obama
@barackobama
119.2M followers
Cristiano Ronaldo
@cristiano
112M followers
Donald J. Trump
@realdonaldtrump
111.8M followers
Narendra Modi
@narendramodi
107.1M followers
Rihanna
@rihanna
98M followers
NASA
@nasa
92.2M followers
Justin Bieber
@justinbieber
91.2M followers
KATY PERRY
@katyperry
88.4M followers
Taylor Swift
@taylorswift13
82.3M followers
Lady Gaga
@ladygaga
73.8M followers
Virat Kohli
@imvkohli
71.1M followers
Kim Kardashian
@kimkardashian
70.1M followers
YouTube
@youtube
68.7M followers
Bill Gates
@billgates
64.3M followers
Neymar Jr
@neymarjr
64M followers
The Ellen Show
@theellenshow
62.4M followers
CNN
@cnn
61.8M followers
Selena Gomez
@selenagomez
61.5M followers
X
@x
60.8M followers