Cross-Chain Messaging Compared: LayerZero vs CCIP vs Wormhole

By Chanuka Geekiyanage Oct 27, 2026

Choosing a cross-chain messaging protocol decides who can forge a message that moves your tokens, and in 2026 that question stopped being theoretical. After the April 18 Kelp DAO exploit, in which about 116,500 rsETH (roughly $292 million) was minted against forged messages on a LayerZero-powered bridge, teams and users have been re-checking how LayerZero, Chainlink CCIP, and Wormhole each verify transfers. This article compares the three on security design, configuration risk, fees, chain coverage, and fit, so you can decide which one to trust with your tokens or your own deployment.

Panaprium ist unabhängig und wird vom Leser unterstützt. Wenn Sie über unseren Link etwas kaufen, erhalten wir möglicherweise eine Provision. Wenn Sie können, unterstützen Sie uns bitte monatlich. Die Einrichtung dauert weniger als eine Minute und Sie werden jeden Monat einen großen Beitrag leisten. Danke schön!

The Short Answer

If you move or hold large value on a bridged asset, check which protocol secures it and how it is configured, because that matters more than brand. For most readers, the safest pick for high-value transfers right now is CCIP or a well-configured multi-verifier LayerZero setup. Wormhole is the practical choice when Solana or non-EVM reach matters most.

Situation	Recommended Option	Why
Issuing a new token across many chains	LayerZero (multi-DVN, pinned config) or CCIP (CCT)	Both support burn-and-mint token standards with issuer control
High-value or institutional assets	CCIP	Separate risk-monitoring layer and no per-app verifier choice to get wrong
Solana or non-EVM heavy routes	Wormhole, or CCIP now that v1.6 added Solana	Wormhole has long Solana history and a fixed, uniform guardian set
You want custom security thresholds.	LayerZero	Apps choose their own verifiers and quorum
You just want to bridge tokens as a user	Use an aggregator, check the asset’s issuer setup	The protocol matters less than how the token is configured

For a wider ranking that includes Axelar, Hyperlane, and others, see this comparison of the best cross-chain messaging protocols.

What the Kelp Exploit Changed

The attacker did not break LayerZero’s core contracts. According to LayerZero’s incident account, attackers poisoned internal RPC nodes used by the LayerZero Labs verifier (DVN) while also launching a DDoS attack on its external RPC providers. The verifier then signed off on messages for transfers that never happened. LayerZero attributes the attack to North Korea-linked actors.

The key detail is configuration. Kelp’s rsETH bridge required a single verifier, the LayerZero Labs DVN, which is called a 1-of-1 setup. One compromised verifier was therefore enough. LayerZero says Kelp chose that setup against its advice, and reported that Kelp had earlier moved from 2-of-2 to 1-of-1. Kelp disputes this and says 1-of-1 matched LayerZero’s documented defaults. A September 2026 lawsuit makes similar claims, but those are allegations, not findings.

Both sides agree on the outcome. LayerZero later admitted it should not have allowed its DVN to act as a sole verifier for high-value transfers. It stopped serving 1-of-1 configurations and is migrating default settings to at least 5 verifiers where possible, with a floor of 3. A Dune analysis cited in press coverage found 47% of active LayerZero apps still ran 1-of-1 at the time.

The market reacted. Kelp said it would move rsETH to CCIP, and Solv Protocol announced a migration of about $700 million in SolvBTC and xSolvBTC. Kraken, Re, and Huma were also reported to be moving.

The lesson is not “LayerZero bad, CCIP good.” It is that a protocol with configurable security is only as safe as the configuration, and defaults can be a trap.

Image source: LayerZero V2 Docs

How Each Protocol Verifies a Message

The three differ on one question: who decides whether a message is real, and who controls that choice?

Protocol	Verification	Who Sets Security	Main Weakness	Best For
LayerZero V2	Verifiers (DVNs) chosen per app, X-of-Y-of-N	The app developer	Weak configs, such as 1-of-1	Teams that will actively manage security
Chainlink CCIP	Chainlink oracle networks plus a separate Risk Management Network	Mostly the protocol, with issuer-set limits	Less flexibility, config still matters	High-value assets, institutions
Wormhole	19 Guardians sign each message, 13 needed	The protocol (same for every app)	One shared validator set for everyone	Solana and non-EVM routes

LayerZero

LayerZero V2 splits the job into endpoints, verifiers, and executors. An app picks its verifier set and quorum, for example 3 of 5. That flexibility is the strength and the risk.

Strengths: very broad ecosystem reach, strong token standard adoption (OFT), and room to design security around your risk. Weaknesses: the Kelp incident shows weak defaults can ship to production, and LayerZero Labs has acknowledged earlier operational mistakes, including a past multisig signer error it says it has since fixed. Best for teams with security staff who will pin configs, use multiple independent verifiers, and avoid relying on defaults.

Chainlink CCIP

CCIP uses Chainlink’s oracle networks to carry messages and adds a Risk Management Network, which is a separate set of nodes that can block suspicious transfers. Token issuers can also set rate limits on how much value moves. The Block reported that CCIP involves 16 independent node operators.

Strengths: defense in depth, rate limits, and a reported record of no major losses since launch. Weaknesses: less configurable than LayerZero, and fees include a network component. CCIP 2.0 introduces configurable cross-chain verifiers, and Chainlink’s own docs warn that outcomes depend on how issuers and verifiers configure things. Best for stablecoins, tokenized assets, and tokens where a security failure would be costly.

Wormhole

Wormhole relies on 19 Guardians, and a Verified Action Approval needs 13 signatures. Security is the same for all apps, which makes it easy to reason about but impossible to customize. Extra checks include Governor, a global token flow monitor, and Global Accountant, which tracks supply across chains.

Strengths: deep Solana history, the NTT token standard, and a long run since the 2022 exploit. That exploit, on February 2, 2022, saw an attacker forge a signature check on Solana and mint 120,000 wETH worth about $326 million. Jump Crypto replaced the ETH. Weaknesses: one shared Guardian set for every app, and coverage can shrink, as when Wormhole fully deprecated Scroll on April 21, 2026, citing security. Best for Solana and non-EVM routes where you accept a fixed trust model.

Fees, Speed and Chain Coverage

Fees are the hardest part to compare honestly, because they depend on route, token, and gas that day. CCIP states its formula: total fee equals a blockchain fee plus a network fee, and developers can call getFee() to quote it before sending. LayerZero prices verifier and executor work per message, and Wormhole reportedly charges no protocol fee for most products, so you mostly pay gas and any relayer cost. Always quote a real transfer instead of trusting a table.

Coverage counts conflict across sources, so treat them as rough:

LayerZero: published estimates range from 70+ to 130+ chains depending on what is counted.
CCIP: about 60 networks in early 2026 reporting, with v1.6 adding Solana support in July 2026.
Wormhole: over 40 chains as of May 2026.

Check each protocol’s own directory for your exact route before committing.

How to Evaluate a Bridged Asset Before Depositing

Most users never pick the messaging protocol directly. They hold a token that someone else bridged. Check these things first:

Which protocol secures the token, and is it documented by the issuer?
For LayerZero tokens, how many independent DVNs are required, and is the config pinned rather than default?
Who runs the verifiers, and are they genuinely independent?
Does the token have rate limits or a supply monitor, such as CCIP rate limits or Wormhole’s Global Accountant?
Who can upgrade the contracts, and through what multisig or governance?
How much of the token’s value sits in one bridge, and is the asset used as lending collateral elsewhere?

That last point matters because Kelp’s failure spread beyond Kelp. Aave’s TVL reportedly fell by about $8.9 billion to $17.5 billion as the market priced in rsETH risk. If you chase yield across chains, see how cross-chain yield aggregators handle bridge risk before depositing.

Image source: defillama.com/protocol/layerzero

Common Mistakes

Trusting default settings. Defaults are chosen for easy setup, and the Kelp case shows they may not match your risk.
Treating “no hack yet” as proof of safety. A clean record is evidence, not a guarantee.
Using one protocol for everything. Concentration in a single bridge multiplies the damage of one failure.
Ignoring off-chain infrastructure. The Kelp attack hit RPC nodes, not smart contracts, so audits of contracts alone would not have caught it.
Moving full size on a new route. Send a small test transfer first and confirm arrival and fees.

My Take

For high-value assets, I would pick CCIP today, mainly because it removes the most dangerous user-facing choice: a weak verifier setup. The Risk Management Network and rate limits add layers that a single compromised component cannot easily defeat. The cost is less flexibility, and CCIP 2.0 shows that configuration risk is moving there too, so check how each token is set up.

I would still use LayerZero, but only where multiple independent verifiers are required, configs are pinned, and the team can explain its setup. The reported 1-of-1 share across LayerZero apps is the figure I would check against any specific token. LayerZero’s response, ending 1-of-1 support and raising default quorums, is a real improvement, but it came after the loss.

I would use Wormhole for Solana and non-EVM needs, and I would accept its fixed trust model knowingly. Its single shared Guardian set is a concentration risk, but its design is simple and has run without an exploit since 2022, as far as I could verify.

Avoid any of them if the asset’s issuer cannot tell you who verifies its messages. Before using any bridged token, I would check the verifier count, who operates the verifiers, who can upgrade contracts, and whether rate limits exist.

Conclusion

The best choice depends on what you are protecting. CCIP is the safer default for high-value assets, LayerZero is strong when run with multiple independent verifiers and pinned settings, and Wormhole fits Solana and non-EVM routes where you accept a fixed trust model. The biggest tradeoff is flexibility versus safe defaults.

The biggest risks are weak verifier setups, shared validator sets, and off-chain infrastructure that audits do not cover. Concentration also matters, because a failed bridged asset can hurt lending markets that accept it.

Your next step is practical. Pick the bridged tokens you hold, find which protocol secures each one, and confirm the verifier count and rate limits before adding more size.

FAQs

1. Is LayerZero still safe to use after the Kelp exploit?

LayerZero says the core protocol was unaffected and that the loss involved one app, about 0.36% of assets on the network. It now refuses to serve 1-of-1 setups, but you should still confirm any token you hold uses multiple independent verifiers.

2. Is Chainlink CCIP safer than LayerZero?

CCIP has a reported clean record and extra layers such as the Risk Management Network, but it has a shorter and smaller track record than some rivals. Its safety also depends on how each token issuer configures it.

3. Did Wormhole recover from its 2022 hack?

Yes, Jump Crypto replaced the 120,000 ETH within about a day, so users were made whole. The exploit was a signature-verification flaw on Solana, and the protocol has added monitoring layers since.

4. How do I find out which protocol secures a bridged token?

Check the token issuer’s documentation or the protocol’s explorer, such as the CCIP directory or LayerZero’s docs and scan tools. If an issuer does not publish this, treat that as a risk signal.

5. Which protocol has the lowest fees?

It depends on the route and day, and Wormhole reportedly charges no protocol fee for most products while CCIP and LayerZero charge per message. Quote the actual transfer before you send.

References

The Block, KelpDAO sues LayerZero over rsETH exploit: https://theblock.co/news/regulation/2026-09-25-kelpdao-sues-layerzero-claims-it-endorsed-setup-used-in-292-million-rseth-exploit-416361.

DeFi Prime, The KelpDAO rsETH Exploit: https://defiprime.com/kelpdao-rseth-exploit

LayerZero, An Overdue Apology: https://layerzero.network/blog/an-overdue-apology

The Block, LayerZero public apology for Kelp DAO response: https://www.theblock.co/post/400629

War dieser Artikel hilfreich für Sie? Bitte teilen Sie uns in den Kommentaren unten mit, was Ihnen gefallen oder nicht gefallen hat.

About the Author: Chanuka Geekiyanage

Chanuka is a content writer, editor and contributor at Panaprium, specializing in long-form editorial articles. He conducts in-depth research and produces well-structured, carefully edited content with a strong focus on clarity, SEO best practices, and consistent formatting. His work spans lifestyle, fashion, wellness, and technical topics, and all articles are reviewed and refined to meet Panaprium’s editorial standards.

Wogegen Wir Kämpfen

Weltweit-Konzerne produzieren in den ärmsten Ländern im Übermaß billige Produkte.
Fabriken mit Sweatshop-ähnlichen Bedingungen, die die Arbeiter unterbezahlt.
Medienkonglomerate, die unethische, nicht nachhaltige Produkte bewerben.
Schlechte Akteure fördern durch unbewusstes Verhalten den übermäßigen Konsum.
- - - -
Zum Glück haben wir unsere Unterstützer, darunter auch Sie.
Panaprium wird von Lesern wie Ihnen finanziert, die sich unserer Mission anschließen möchten, die Welt völlig umweltfreundlich zu gestalten.

Wenn Sie können, unterstützen Sie uns bitte monatlich. Die Einrichtung dauert weniger als eine Minute und Sie werden jeden Monat einen großen Beitrag leisten. Danke schön.