@bittybitbit86 @dawiddrzala @LayerZero_Core They’re shady. They still haven’t dropped the post mortem because it’s just that bad in relation to how it was executed and they’re trying to muddy it to not look as severe
English
Archive
665 posts
@dawiddrzala @LayerZero_Core Yeh I think the way they handled things has really put teams off them.
English
Let me tell you how bad it is for @LayerZero_Core, these decisions are not taking lightly, those teams now depreciating L0 bridges would have done so after full assessment of their stack and concluded that risks were not worth taking.
Layerzero is effectively dead.
Kraken@krakenfx
Kraken is deprecating its existing cross-chain provider and migrating to @Chainlink CCIP as its exclusive cross-chain infra to secure Kraken Wrapped Bitcoin (kBTC) & all future Kraken Wrapped Assets. Kraken chose Chainlink CCIP because it offers enterprise-grade infrastructure with strict security & risk management requirements, including: • ISO 27001 and SOC 2 Type 2 certifications • Secure by default architecture • 16 independent nodes • Native rate limits, and more. Together, Chainlink and Kraken can help accelerate the global adoption of crypto by unlocking utility and distribution for all Kraken Wrapped Assets across DeFi. For kBTC customers, no action is required. More details on the migration process to follow on official Kraken channels.
English
@PriyankGupta03 Their tech has always been fundamentally flawed if you’ve followed it from its inception
English
Plenty of protocols have gotten hacked and bounced back stronger than ever.
It isn't the 'hack' that is causing this flight.
🟩 Ibrahim@Ikh011
LayerZero has lost $4B in TVL after 5 major protocols migrated to Chainlink's CCIP You get hacked once and its over
English
@AirdropGlideApp @LayerZero_Core Only usdt0
Tether Investments announced a strategic investment in LayerZero Labs on February 10, 2026, to bolster cross-chain interoperability for USDt0,
English
This whole situation is crazy.
Will there be any significant projects remaining using @LayerZero_Core at this point?
Impressive how suddenly CCIP is the pinnacle of bridging technology.
As as Cosmos fan, it's painful not to see IBC get a look in, but then support for EVM, in both IBC and Cosmos in general, is ass.
Lombard@Lombard_Finance
Following a comprehensive security review of the cross-chain infrastructure underpinning LBTC and BTC.b: - CCIP will replace LayerZero as the cross-chain infrastructure across Solana, Etherlink, Berachain, Corn, and TAC - LayerZero on Morph and Swell will be fully deprecated
English
@fulltimelinkie If they’re not on the boat now then they never will be 🤷♀️
English
I've been helping people discover $LINK in various corners of the cryptosphere since 2017 at literally 11 cents. I came to Twitter because literally this is your last chance, and I'm trying to help as many people as I can to get on the boat. Started this account at $8.
English
Archive retweetledi
Lido, the largest liquid staking protocol, chose Chainlink CCIP as its official cross-chain infra to secure $20B in wstETH.
@LidoFinance shares the security principles behind the decision and why CCIP exceeded its rigorous security and risk requirements.
DeFi will win.
Lido@LidoFinance
Following recent bridge exploits, Lido contributors are publishing the security principles behind wstETH’s multi-chain strategy, and why @chainlink CCIP was selected as the official cross-chain solution. The analysis covers how Chainlink CCIP delivers strong decentralization, native safeguards, and issuer control as default protocol-level guarantees, which insulates wstETH from a number of attack vectors behind the Kelp / LayerZero exploit. This decision was made last November by the Network Expansion Committee, with CCIP securing wstETH via 16 independent node operators, native rate limiting, and no vendor lock-in over token contracts. Read the full breakdown from Lido contributors: blog.lido.fi/cross-chain-se…
English
@ChainlinkP @nullpackets @SenWarren Epstein amendment here was laughable with how out of place it is
English
@nullpackets @SenWarren I can't believe some of the amendments dems are coming up with. They don't fundamentally understand what this technology is.
English
Plan B
"if you want to force the US's hand - start offshore. Banks have to adhere to international standards"
@senwarren is willing to kill American jobs and punish US crypto holders only for regulatory arbitrage to require the US to choose to become an economic backwater or meet min requirements anyways.
Pass the Clarity ACT @thedemocrats @SenateDems
Senator Cynthia Lummis@SenLummis
Without the Clarity Act, the digital asset industry will move offshore to any nation that has regulators willing to engage. Every day that we stall is a day we hand our competitors an advantage we won't get back. The Clarity Act is critical to securing our financial future.
English
Archive retweetledi
NEW: Leading crypto exchange @krakenfx is deprecating its legacy cross-chain provider and migrates to Chainlink CCIP.
Starting with kBTC, all current and future Kraken Wrapped Assets will use CCIP for secure distribution across blockchains and global markets.
Kraken@krakenfx
Kraken is deprecating its existing cross-chain provider and migrating to @Chainlink CCIP as its exclusive cross-chain infra to secure Kraken Wrapped Bitcoin (kBTC) & all future Kraken Wrapped Assets. Kraken chose Chainlink CCIP because it offers enterprise-grade infrastructure with strict security & risk management requirements, including: • ISO 27001 and SOC 2 Type 2 certifications • Secure by default architecture • 16 independent nodes • Native rate limits, and more. Together, Chainlink and Kraken can help accelerate the global adoption of crypto by unlocking utility and distribution for all Kraken Wrapped Assets across DeFi. For kBTC customers, no action is required. More details on the migration process to follow on official Kraken channels.
English
@AncientMedicin3 @ARiHBARi @CryptoHayes @scottmelker @The_DTCC @chainlink Nah the hyphen was my second clue. It was how the tweet started. Very reminiscent of AI
English
@PaperlessChains @ARiHBARi @CryptoHayes @scottmelker @The_DTCC @chainlink Just because there is use of a hyphen doesn’t automatically mean it was AI 😆
English
🚨 @CRYPTOHAYES & @SCOTTMELKER TRY TO DISCREDIT @THE_DTCC & @CHAINLINK PARTNERSHIP BY SAYING "OVER TIME WE SEE THAT NONE OF THESE DEALS MEAN ANYTHING" BECAUSE "IT DOESN'T MOVE THE TOKEN🚨
$LINK
English
I stepped away from the conference circuit in Q1 and early Q2 because my wife was pregnant with our second child, and I wanted to stay grounded and present at home.
In mid-March, we lost our baby in the third trimester. The grief has been heavy.
Building a startup rarely leaves space for extended grief or going off the radar. There’s constant pressure to keep moving. I’ve never been a believer at all in traditional “work-life balance.” To me, there’s success or there isn’t, and real success starts with ensuring my wife and family are cared for to the fullest extent possible. Everything else flows from that. Work then is every other remaining waking moment.
As a co-founder of a 13-person startup, I feel the weight of responsibility daily. Twelve other people’s livelihoods depend on the momentum we maintain. I’m incredibly fortunate to have the team I do, they immediately told me to take all the time I needed. We spent a week in the hospital, and they held things down without hesitation.
You build, you grow, you keep moving forward. Life is full of unexpected lessons. It reminds me of the old Buddhist parable of the farmer’s son: the horse runs away (bad?), comes back with more horses (good?), the son breaks his leg riding a new wild horse (bad?), and then can’t go to war (good?), and so on. We rarely know in the moment what something truly means.
If you’ve made it this far in the post, please know this isn’t a request for condolences. This is simply life, its struggles, its beauty, and its demand that we keep going. We don’t forget. We honor and remember. And we continue because we still have the gift of another day.
This post is for anyone who has quietly carried similar pain while still showing up for work, family, and responsibilities. These things often go unspoken. I had many people ask me why I’ve not been at recent large events, so this is why.
This feels especially relevant to share on here too.
When you’re arguing with someone online or attacking them over a differing viewpoint, remember: there’s a real person on the other side of the screen.
Pause before you post. Think for a moment. Crypto Twitter (CT) could use more of that pause right now.
Few people can hold two opposing views in their head at once anymore; learn a thing or two from my friend @Shenanigrahams. That’s what kind of discourse we need to move the industry forward.
With that said, I’m stepping back into the conference circuit in the coming weeks as we head into the next quarter stretch before mainnet. First up: @proofoftalk in Paris, hosted in none other than the Louvre.
Excited to reconnect, share what we’ve been building at @ZenithFdn, and move forward.
Proof of Talk@proofoftalk
Heslin Kim @HeslinKim, Co-Founder & CBO of @ZenithFdn, takes the Proof of Talk stage this June on the Canton Track. Zenith is building the EVM execution layer for Canton, letting Ethereum devs and institutions deploy on the same infra with privacy, compliance, and atomic settlement built in. They're a Super Validator on Canton with the maximum weight of 10. Alongside @jpmorgan, @HSBC, @Visa, and @The_DTCC. Heslin has spent 10+ years in digital assets and tokenized securities. At the Louvre he's talking cross-VM architecture, app composability, and bridging DeFi to institutional-grade onchain finance. June 2–3. Louvre Palace, Paris. The Davos of Web3. tickets.proofoftalk.io/passes
English
@AncientMedicin3 @ARiHBARi @CryptoHayes @scottmelker @The_DTCC @chainlink Man you really used AI for this?
English
This isn’t a sandbox or a pilot.
This is critical infrastructure of the DTCC locking in Chainlink’s stack as a mechanism for day to day operations.
Here’s the part you two seem to have missed or ignored…
Whether services are paid directly via ethereum:0x514910771af9ca656af840dff83e8264ecf986ca, indirectly via Payment Abstraction or Off Chain arrangements—ALL means of revenue are structured to drive value capture to the token.
The team has spoken about this extensively and still has a massive number of tokenomic flywheel updates which have apparently been held off on, waiting for CLARITY to codify federal laws before updating.
All that said, this is the biggest and most significant announcement in the history of the entire industry and just because the token didn’t rage pump (retail absent, no Clarity yet, utility hasn’t started yet, etc) hardly implies that this isn’t real and going into utility imminently (Q4 launch).
Load up and lock in or get left the fuck behind.
English
Archive retweetledi
You want to know why $LINK marines went ballistic over the LayerZero incident? Because in addition to us calling out the design and team years ago - all the suggested "fixes" - rate limits, timelocks, out of band monitoring - by helpful industry thot leaders - have been suggested for years with no accountability.
Only Chainlink CCIP has supported all of these by default but still the industry repeats it mistakes over and over again.
run ⬡ the ⬡ juels@nullpackets
ERC677 = Stateful = TCP ERC20 = Stateless = UDP CCIP = Stateful = active Risk Management Every other blockchain bridge = Stateless = passive/no risk management CCIP is the new TCP/IP The Risk Management Network is the new <firewall vendor you think most secure> #DeFI #crypto
English
This chick is really going off the rails about CLARITY 🤣. I appreciate the idealism, I really do. I live in a pragmatic mindset, despite my pessimistic opinions of the world. Just buy $LINK and win.
Wendy O@CryptoWendyO
The Clarity Act is a joke. - Retail is getting absorbed into the predatory finance system which does NOT give equal access like crypto did - No real developer protections - Warren speaking out without reading - Don’t even ask about the emoji, you know
English
@Flowslikeosmo They still haven’t even dropped an actual post mortem meaning they’re probably muddying it up as much as possible to save their own credibility
English
Everyone's watching the LayerZero fallout narrative.
Kelp's migration to CCIP.
Stargate V2 has seen fees drop by nearly 50% over the last 30 days.
The bridge security discourse has completely consumed the conversation about who wins in the long term across chains.
But while everyone's watching this story play out, the actual fee leader in bridging right now isn't Stargate, Across, Wormhole, and it's not LayerZero V2.
It's @near_intents. A quick comparison:
- $2.99M in bridge fees over the last 30 days
- LayerZero generated $154K over the same window.
Stargate V2 generated $107K.
Intents is doing more in fees than both of those combined, 19x more actually.
I think $NEAR hasn't priced in any of this when you consider the supply-diminishing mechanisms.
Fee switch + a halved inflation rate + burn on base-layer gas fees
Data: @tokenterminal
English
$290M drained.
One DVN. One point of failure.
The KelpDAO exploit proved 1-of-1 DVN configs aren't enough.
A second DVN only protects you if it's truly independent.
Ours is; and we're live on @LayerZero_Core 👇
English
@FrankRemoulada These people are delusional. Why would you think the US government would use infra that got hacked by North Korea after the fact. Makes no sense whatsoever
English
Yes I want to use LayerZero so the Office of Foreign Asset control comes knocking on my door asking about using infrastructure that was breached by a hostile nation state, and the vibes
BigBrain Less@bigbrainless
When devs want omnichain apps and real interoperability… They look at LayerZero 👀 Positive vibes. Fast innovation. Real builder energy. Meanwhile Chainlink maxis still fighting on Twitter 😭 $ZRO
English
@mayorkazzy @CryptoticT @LayerZero_Core Mistakes weren’t corrected for years after they were told about them and brushed them off. Sorry to say but things are not looking up for them after this
English
@CryptoticT @LayerZero_Core It's always been institution and obviously they choose LZ! I agree the situation is shitty. But knowing the LZ team, this won't be their downfall. Mistakes were made and now they are all getting corrected. In the tech level, LayerZero remains the best interoperability option.
English
Instead of trying to bring LayerZero down by the whole situation, why not make your tech better so it had naturally been chosen against LayerZero?
@LayerZero_Core will survive this and continue to be the num 1 interoperability infrastructure.
This will only make them stronger
James@mayorkazzy
All the hate around @LayerZero_Core is a desperate effort from the link marines to win a battle that has already been won by LayerZero, no 1 in the interop game. As I do agree that LZ has their fault in the whole situation, but the hate is being blown out of proportion.
English
Archive retweetledi
People are still sleeping on just how unimaginably poor LayerZero opsec actually was:
In their apology blog, LayerZero describes the one multisig signer trading memecoins as a single isolated event just involving one person.
However, as CLG points out via the onchain evidence:
In reality, the multisig signer attempted multiple memecoin trades over the span of a year and stayed on the multisig for nearly two years after the first memecoin trade, before finally being rotated off
Furthermore, there were actually 3 signing addresses that were engaged in non-multisig related activity (memecoin trading, DEX swaps, bridging, LP provisioning) on a 2-of-5 Gnosis Safe multisig.
So, there were *THREE* addresses doing clown fiesta stuff over the course of *YEARS.* LayerZero's blog only briefly mentioned what one address was doing. They entirely avoided even discussing the others.
So, LayerZero's private key incompetence is a pick your poison adventure:
They either had three highly irresponsible people on their multisig for years
OR
They put what is supposed to be three separated private keys in the hands of *ONE* person
Either way, they showed they have absolutely zero regard for security.
Zach Rynes | CLG@ChainLinkGod
This new post from @LayerZero_Core directly contradicts Bryan's claim yesterday that the LayerZero Labs multisig signer who was trading the "McPepes" memecoin on Uniswap was just "testing the PEPE OFT integration" Turns out that gaslighting doesn't work when people can check the chain and verify for themselves Naturally, they attempt to minimize the issue by making it seem like this was a one time incident, involving only one signing key, and that the memecoin trader was quickly rotated off the multisig In reality, the multisig signer attempted multiple memecoin trades over the span of a year and stayed on the multisig for nearly two years after the first memecoin trade, before finally being rotated off Furthermore, there were actually 3 signing addresses that were engaged in non-multisig related activity (memecoin trading, DEX swaps, bridging, LP provisioning) on a 2-of-5 Gnosis Safe multisig Billions of dollars in OFT value was exposed to the risk of being exploited by a multisig whose majority threshold of signers failed to practice even the most basic opsec and key isolation practices, FOR YEARS This was not a one-time error oopsie, this was a complete disregard for opsec -- Timeline of events of the LayerZero memecoin trader multisig signer: March 1, 2023 - 0xf1f5E swaps 0.198548 ETH for 1,727,120 McPepes (PEPES) December 21, 2023 - 0xf1f5E calls approve() for Uniswap on the McPepes ERC20 contract April 20, 2024 - 0xf1f5E attempts to sell McPepes on Uniswap but the transaction reverts January 27, 2025 - 0xf1f5E is finally rotated off LayerZero’s Gnosis Safe multisigs and signing threshold changed -- More context in following tweets
English
LayerZero finally posted their incident update. Read it carefully because there’s a lot in there that’s easy to miss.
Lazarus Group, North Korea’s state-sponsored hackers, attacked LayerZero’s internal RPC infrastructure. Poisoned their data. Simultaneously DDOSed their backup. Coordinated, professional, nation-state level.
This wasn’t some random kid finding a bug. This was a targeted attack on cross-chain infrastructure by the same group that’s stolen billions from crypto over the years. The industry keeps treating security like a checklist and these guys treat it like a job.
LayerZero also made their own mistake worse.
Their DVN was running as a 1/1 on high-value transactions. one verifier, no backup, one point of failure. They built the whole protocol to avoid exactly this kind of risk. Then didn’t catch it in their own setup.
They said that directly. No excuses. No pointing fingers at the developer who misconfigured. Just: we didn’t police it, we should have, we own it.
Honestly? That hit differently. Most protocols in this situation spend three weeks writing a post about why technically it wasn’t their fault. LayerZero led with an apology.
Now look at what happened after April 19th.
$9B+ moved across the protocol. Cumulative volume went from zero to $100B+ in three weeks.0.14% of applications affected. The rest kept running.
Survived a nation-state attack and kept growing. That’s not nothing.
But the 1/1 DVN thing keeps me up a little.
How many other bridges are sitting on the same configuration right now? Most developers don’t think about this and uses default.. They trust it’ll be fine. Until it isn’t.
LayerZero moving to 5/5 defaults is the right call. Should have happened before the exploit. But it’s happening now and that matters.
If you’re building anything cross-chain, go check your DVN configuration today.
LayerZero@LayerZero_Core
English
@Web3Panda They were removed from the multisig last year and have activity spanning 3 years. So it’s kinda obfuscating/burying/minimizing the extent to which that signer remained on. Plus it was 3 different addresses doing seperate activity. It seems like they can’t tell the truth
English
