LayerZero V2 represents a fundamental redesign of how cross-chain messaging security is structured. Where LayerZero V1 used a single oracle (Chainlink) and a single relayer to verify messages between chains, V2 decentralizes this entirely — letting every application choose its own combination of independent “Decentralized Verifier Networks” (DVNs) to verify messages. This modularity means a high-value DeFi protocol can require three independent DVNs (e.g., Chainlink, Polyhedra, and Google Cloud) while a gaming project can use just one for lower cost. V2 also introduced ZRO — LayerZero Labs’ governance token — and launched the Omnichain Fungible Token (OFT) standard that has become a dominant primitive for issuing tokens that are natively multi-chain rather than bridged.
Why V2? What Was Wrong With V1?
LayerZero V1 (launched 2022) was architecturally simpler: every cross-chain message required confirmation from:
- An oracle (Chainlink on most chains) — delivered the block header
- A relayer (defaulted to LayerZero Labs relayer) — delivered the transaction proof
The oracle+relayer combination created what protocol designers call “1-of-2 multisig” security. If either was compromised independently, the system remained safe. If both were compromised — or if the oracle and relayer colluded — a malicious message could be injected.
Problems with V1:
- Single oracle assumption (hard dependency on Chainlink)
- Labs-operated default relayer was a centralization vector
- No application-level customization of security assumptions
- Single shared security model applied to all applications equally — no trade-off between cost and security
V2’s Solution: Configurable Security Stacks
V2 replaces the oracle+relayer model with Decentralized Verifier Networks (DVNs):
- Any organization can operate a DVN
- Current DVNs include: Polyhedra Network, Google Cloud, Nethermind, BlockDaemon, Animoca, OKX, and others
- Applications configure a Required DVN list and an optional Optional DVN list
- A message is valid only when the required quorum of DVNs has verified it
Example configurations:
- Maximum security (DeFi): 3 required DVNs (Chainlink, Polyhedra, Google Cloud) + 2 optional
- Balanced (mid-tier DApp): 2 required DVNs (Nethermind + Polyhedra)
- Low cost (gaming): 1 required DVN
This design means security is application-configurable, not protocol-global.
V2 Architecture: How It Works
The protocol is built around the following components.
Message Flow in V2
- Application sends: Source chain application calls LayerZero Endpoint with destination chain address and message payload
- Executor picks up: Off-chain Executor detects the outbound event and begins cross-chain message delivery
- DVNs verify: Each configured DVN independently receives the block hash from the source chain and verifies the message inclusion proof
- Threshold reached: Once the required DVN quorum has verified, the message is marked clear
- Delivery: Executor delivers and executes the message on the destination chain
Key separation: Security (DVN verification) and execution (Executor delivery) are separated. You can use multiple DVNs for security while any party can operate an Executor.
MessageLib: Versioned Security Libraries
V2 introduces the concept of MessageLibs — versioned, upgradeable libraries that define how messages are sent and verified. Applications pin to a specific MessageLib version:
- ULN304 (Ultra Light Node): The V2 default library; uses DVN verification
- Applications can upgrade to newer MessageLibs as the protocol evolves
- Upgrading MessageLib changes the verification mechanism — powerful but requires governance or app-level decisions
Executor Role
Executors handle the mechanical delivery and execution of messages on destination chains. Key properties:
- Fully permissionless — anyone can run an executor
- Executors are compensated per message delivery
- Apps pre-fund execution by depositing gas into the endpoint on source chain
- If an executor fails, another can step in (permissionless delivery)
OFT: Omnichain Fungible Token Standard
One of LayerZero V2’s most adopted primitives is the OFT (Omnichain Fungible Token) standard — a token standard where the canonical supply exists natively on every chain rather than being “bridged” copies.
How OFT Works
Instead of: deploy token on Ethereum → bridge copies to L2s
OFT model: deploy natively on each chain → lock/mint/burn are coordinated via LayerZero messages
Result: No wrapped tokens, no bridge contract holding large reserves. Total supply is maintained mathematically across chains via LayerZero messages.
OFT Adoption
As of 2025, OFT is used by hundreds of projects including:
- JTO (Jito, Solana LST governance token)
- WLD (Worldcoin) for cross-chain transfers
- USDT0 — Tether’s experimental OFT-based dollar
- Multiple RWA tokens seeking native multi-chain presence
ZRO Token
ZRO launched via airdrop in June 2024 — one of the most anticipated token launches of the year due to LayerZero V1’s massive transaction volume.
ZRO Basics
| Property | Detail |
|---|---|
| Launch Date | June 2024 |
| Airdrop | “Proof of Donation” — users donated any amount to Protocol Guild (Ethereum contributors) to claim; Sybil filtering eliminated many accounts |
| Utility | Protocol governance; may be used for fee payments |
| Controversy | “Proof of Donation” requirement divided community opinion |
Airdrop Controversy
LayerZero’s airdrop mechanism required users to make a charitable donation (even $0.01 to Protocol Guild) to claim ZRO. Bryan Pellegrino (LayerZero CEO) argued this was a Sybil-resistance mechanism. Critics argued it was:
- Punishing genuine users who didn’t want to donate
- Creating gaming opportunities (mass $0.01 donations)
- A PR move using charitable framing on what was primarily a Sybil filter
Despite controversy, ZRO launched and has maintained market cap above $500M.
V2 vs Competitors
The following sections cover this in detail.
LayerZero V2 vs Wormhole
| Dimension | LayerZero V2 | Wormhole |
|---|---|---|
| Security Model | Configurable DVN quorums | Guardian set (19 nodes) |
| Token Standard | OFT | NTT (Native Token Transfers) |
| Chain Coverage | 70+ endpoints | 30+ |
| Customizability | Per-application | Limited |
LayerZero V2 vs Axelar
| Dimension | LayerZero V2 | Axelar |
|---|---|---|
| Security Model | DVNs (app-configurable) | PoS validator set |
| Message Type | General purpose | General purpose |
| Token Transfer | OFT native | XERC20 wrapped |
| On-chain Trust | Minimal (Endpoint + DVNs) | Full Axelar chain |
LayerZero V2 vs Across Protocol
Across is specifically intent-based for cross-chain asset transfers; LayerZero V2 is a general messaging protocol. Across is faster for human-facing token transfers; LayerZero V2 is better for cross-chain contract-to-contract communication.
Adoption and Metrics
Cross-chain activity (2024–2025):
- LayerZero V2 processes millions of cross-chain messages monthly
- OFT standard adopted by 500+ projects
- Active on 70+ chains including Ethereum, Solana, Tron, all major L2s, Move VMs
V1 → V2 Migration:
- Most V1 integrations have migrated or are migrating to V2
- V1 endpoints remain live for backward compatibility
- Protocol encourages V2 adoption via DVN marketplace and better tooling
How to Use LayerZero V2
As a token holder (ZRO): Obtain on major CEXes (Binance, Coinbase, OKX) or DEXes. Use in governance voting for LayerZero parameter changes. See for ZRO trading.
As a developer: Deploy your token as an OFT using LayerZero’s SDKs; configure DVNs based on security requirements; integrate LayerZero Scan for cross-chain message monitoring.
Hardware security: Store ZRO long-term with a hardware wallet — .
Related Terms
Sources
Pellegrino, B. et al. (2023). LayerZero V2: An Omnichain Interoperability Protocol. LayerZero Labs Technical Documentation.
Zamyatin, A. et al. (2021). SoK: Communication Across Distributed Ledgers. Financial Cryptography Conference 2021.
Qin, K., Zhou, L., & Gervais, A. (2022). Quantifying Blockchain Extractable Value: How Dark Is the Forest? IEEE Symposium on Security and Privacy 2022.
Gudgeon, L. et al. (2020). DeFi Protocols for Loanable Funds: Interest Rates, Liquidity, and Market Efficiency. ACM Conference on Advances in Financial Technologies.
Dang, H., Dinh, T.T.A., Loghin, D., Chang, E.C., & Ooi, B.C. (2019). Towards Scaling Blockchain Systems via Sharding. ACM SIGMOD Conference 2019.