LayerZero vs Wormhole: Verification Models Compared
Quick answer. LayerZero apps pick their own verifiers (DVNs) per route, so security depends on that setup. Wormhole messages need signatures from 13 of 19 Guardians, one set shared by every app and governed by those Guardians.
Video transcript
LayerZero and Wormhole both move messages between chains. The difference is who decides a message is real. Disclosure: LayerZero is a Guardian client, and we hold both to the same standard.
LayerZero apps pick their own verifiers, called DVNs, for each route. Every required DVN must attest, plus enough optional ones to meet a threshold. Unset routes fall back to defaults that can change.
Wormhole uses one shared set of 19 Guardians. A message is valid once 13 of 19 sign, for every app.
LayerZero Endpoints are immutable, so the app's keys are the main lever. In Wormhole, the same Guardian supermajority that verifies messages also approves core upgrades.
In 2022, a Wormhole contract bug let an attacker spoof Guardian signatures. In 2026, Kelp DAO lost about 292 million dollars on a route whose only verifier was fooled, and neither incident broke a full quorum.
For tokens, both standards let issuers choose verifiers. OFT relies on its route's DVNs, with optional rate limits. NTT uses transceivers with a threshold, and rate limits are built in.
Each model has its own trap: single DVN or unpinned routes on LayerZero, missing destination checks and loose NTT admin keys on Wormhole. On both, multisig admins, rate limits and change alerts matter as much.
Read the full comparison, or talk to Guardian to check your bridge before it carries value.
Disclosure: LayerZero is a Guardian client. Guardian audits LayerZero's code and verifies USDT0's LayerZero deployments. We hold both protocols to the same standard, citing each one's own documentation and reports.
LayerZero and Wormhole both move messages and tokens between chains. The biggest difference is who decides that a message is real.
That sets who can forge a message and who can change the rules.
Claims below cite each protocol's own docs, as of November 2026. For a third model, see LayerZero vs Chainlink CCIP.
How Each Verifies Messages
LayerZero: the DVNs each app picks
Every LayerZero channel has a security stack: required DVNs, optional DVNs and an optional threshold.
Every required DVN must attest, plus enough optional DVNs to meet the threshold. One missing or conflicting required DVN rejects the message.
The app's delegate sets the stack per chain and direction. Anything left unset falls back to defaults that "may change without notice."
The protocol accepts any stack with at least one DVN. LayerZero's own guidance is at least two required DVNs per channel.
Wormhole: 13 of 19 Guardians
Wormhole relies on 19 nodes called Guardians. A signed message, called a VAA, is valid once 13 of them sign.
Wormhole calls them "real entities with a track record," each with an equal stake.
Ethereum and Solana are secured by all 19 Guardians. On delegated chains, a subset of Guardians observes the chain first. The 13-of-19 signing rule still applies.
| LayerZero | Wormhole | |
|---|---|---|
| Who verifies | DVNs the app names per route | 19 Guardians, shared by all apps |
| Threshold | Every required DVN, plus the optional threshold | 13 of 19 signatures |
| If the app sets nothing | Changeable defaults, some with a Dead DVN | The same Guardian set |
| Finality | Block confirmations, set per route | Consistency level, set by the sender |
| Delivery | Executors; anyone can execute; cannot forge | Executors, "considered untrusted"; cannot forge |
Who Can Change the Security
LayerZero
- Endpoints "cannot be upgraded, paused, or modified by anyone, including LayerZero Labs."
- Message libraries: new versions can be added; deployed ones cannot be changed or removed.
- Defaults: LayerZero Labs can change them "at any time." Pinned settings stay put.
- App settings: the owner sets peers and the delegate. The delegate sets DVNs, executor, libraries and confirmations.
Wormhole
- Governance: Guardians vote by signing. Any action needs a two-thirds supermajority.
- Scope: the Guardian set itself, and upgrades to core and Wrapped Token Transfers contracts.
- Governor: tracks flows across chains and delays transfers that may indicate an exploit.
- App settings: integrators pick finality where a chain allows. NTT issuers set their own controls.
In LayerZero, the app's keys are the main lever, and the Endpoints cannot change. In Wormhole, the same Guardian supermajority verifies messages and approves core upgrades.
Incident History
Wormhole, February 2022
On February 2, 2022, an attacker minted 120,000 unbacked wrapped ETH on Solana. The Block put the loss at about $325 million.
Per samczsun, quoted by The Block, Wormhole "didn't properly validate all input accounts, which allowed the attacker to spoof guardian signatures."
Rekt traced it to Wormhole's Solana contract, which "didn't correctly verify the address being provided."
The next day, Jump Crypto said it "replaced 120k ETH to make community members whole." Wormhole said "all wETH are backed 1:1."
Kelp DAO, April 2026
On April 18, 2026, a forged message on Kelp's Unichain to Ethereum route released 116,500 rsETH, about $292 million, per LayerZero's report.
Poisoned RPC nodes fooled LayerZero Labs' DVN, the route's only verifier. Its signing keys were not compromised.
LayerZero says Kelp had cut a 2-of-2 stack to 1-of-1. Kelp told CoinDesk its setup "followed LayerZero's documented defaults," crypto.news reported. Our Kelp DAO breakdown has both accounts.
Neither loss broke a full multi-party quorum. Wormhole's came from a contract bug, and Kelp's from a route whose quorum was one verifier.
Token Standards: OFT vs NTT
Both standards keep one issuer-controlled token across chains. Their built-in controls differ.
| LayerZero OFT | Wormhole NTT | |
|---|---|---|
| Modes | Burn and mint, or lock and unlock (OFT Adapter) | Burn and mint, or hub and spoke |
| Existing tokens | Adapter wraps the unmodified token | Hub and spoke leaves the original contract unaltered |
| Verification | The route's DVN stack | Transceivers with a threshold, such as 2 of 3 |
| Rate limits | Optional RateLimiter; reverts over the limit | Built in: outbound queues or reverts, inbound delays |
| Pause | Stablecoin OFT: per destination or token-wide | Pauser pauses; only the Owner unpauses |
| Supply check | Not in the OFT docs; reconcile yourself | Global Accountant, set up with Wormhole contributors |
NTT is not limited to Guardians: "Custom verifiers are implemented as transceiver contracts." With only the Wormhole transceiver, a deployment relies on Guardian signatures.
So at the token layer, both let the issuer choose verifiers. Then check:
- OFT: "There can only be one OFT Adapter lockbox in your omnichain deployment."
- OFT: LayerZero says rate limiting "may not be suitable for all OFT applications."
- NTT: Wormhole advises "separating Owner and Pauser roles." The Stablecoin OFT splits pauser and unpauser similarly.
Our OFT security checklist covers the OFT side in depth.
Chain Coverage and VM Support
LayerZero calls its protocol "VM agnostic," naming Ethereum, Solana and Aptos as examples. Our LayerZero reviews span EVM, Solana, Stellar and Canton.
Wormhole's NTT docs cover ERC-20 tokens on EVM chains and SPL tokens on SVM chains.
What matters is verifier depth on your chains:
- LayerZero: "Some chains have only one DVN provider currently deployed." A DVN must be live on both chains.
- Wormhole: on delegated chains, a subset of Guardians does the observing.
Which Fits Which Use Case
Each model has its own integration trap. Our public reports show one of each:
- LayerZero: Olympus encoded "no optional DVNs" as 0, which means "use the default" (M-01, resolved).
- Wormhole: VAAs are "effectively multicast," so apps must check the destination. M0 transfers could be replayed across spokes (C-02, resolved).
| Question | LayerZero | Wormhole |
|---|---|---|
| Who verifies if you set nothing? | LayerZero defaults, which can change | 13 of 19 Guardians |
| Can you choose the verifiers? | Yes, DVNs per route | For NTT, through transceivers |
| Can you run your own verifier? | Yes, as a required DVN | Yes, as a custom transceiver |
| Who can upgrade the core? | No one: Endpoints are immutable | Two-thirds of Wormhole's Guardians |
| Main thing to get wrong | Single-DVN or unpinned routes | Destination checks and NTT admin keys |
Choose LayerZero to pick your own verifiers, if you can pin and check every route yourself.
Choose Wormhole for one shared, established verifier set, if you accept that its Guardians also govern the core.
On both, multisig admin roles, rate limits and change alerts do as much as the verifier model.
How Guardian Helps
Guardian audits LayerZero's code, including its Solana OApp and Console contracts. Since February 2025, we have verified USDT0's peers, DVN sets and confirmations on every pathway.
On Wormhole, our public M0 reports cover replay and finality settings in Wormhole adapters. Our DVN configuration guide lists the LayerZero checks.
Guardian's audits and pentests cover bridge contracts, verifier settings and the offchain systems around them.
Frequently Asked Questions
Is LayerZero more secure than Wormhole?
Neither wins for every app. A LayerZero route is as strong as the DVNs it pins, which can be just one. Wormhole needs 13 of 19 Guardians, who also govern the core. Admin keys and rate limits matter on both.
How many Guardians does Wormhole have?
Nineteen. A message, called a VAA, is valid once 13 of them sign. Wormhole says Ethereum and Solana are secured by all 19, while some chains are first observed by a delegated subset.
What is the difference between a DVN and a Wormhole Guardian?
A DVN is any verifier a LayerZero app names in its security stack, chosen per route. A Guardian is one of 19 Wormhole nodes that sign messages for every app.
What is the difference between OFT and NTT?
An OFT relies on its route's LayerZero DVNs, and rate limits are optional. NTT relies on transceivers with a threshold, and has built-in inbound and outbound rate limits.
Sources
- LayerZero Docs: Security Stack (DVNs)
- LayerZero Docs: DVN and Executor Configuration
- LayerZero Docs: Integration Checklist
- LayerZero Docs: Executors
- LayerZero Docs: Protocol Overview
- LayerZero Docs: OFT Quickstart (EVM)
- LayerZero Docs: Stablecoin OFT Extensions
- LayerZero Docs: DVN Providers
- LayerZero Labs on GitHub: UlnBase.sol, LayerZero V2
- LayerZero: LayerZero Labs KelpDAO Incident Report (May 18, 2026)
- Wormhole Docs: Guardians
- Wormhole Docs: Security
- Wormhole Docs: VAAs
- Wormhole Docs: Native Token Transfers Overview
- Wormhole Docs: NTT Architecture
- Wormhole Docs: NTT Security
- Wormhole Docs: NTT Access Control
- The Block: Wormhole Replenishes Its Blockchain Bridge After $325 Million Exploit (February 3, 2022)
- Rekt: Wormhole, Rekt (February 3, 2022)
- crypto.news: Kelp DAO Blames LayerZero Defaults for $290M rsETH Bridge Disaster (April 20, 2026)
- Guardian: Olympus LayerZero Integration report (June 9, 2026)
- Guardian: M0 Liquidity Delivery report (January 30, 2026)
- Guardian: M0 PYUSDX report (May 24, 2026)
- Guardian: USDT0 Deployment and Configuration Verification case study
Check your bridge before it carries value
Guardian reviews your verifier settings, rate limits and admin keys on LayerZero or Wormhole, and the contracts behind them.