LayerZero

LayerZero's V2 announcement on December 14, 2023 described an omnichain messaging protocol with endpoints, DVNs, Executors and an X-of-Y-of-N security model. Its current documentation describes source and destination endpoints, per-channel nonces, message libraries, verification and destination execution.

The model is intentionally modular: applications choose required and optional DVNs and thresholds. That makes LayerZero less like one bridge with one validator set and more like a transport layer whose security depends on the OApp's selected stack and the underlying chains and operators.

Independent contemporaneous reporting places ZRO's token-generation event and first claims on June 20, 2024. The unusual proof-of-donation claim mechanism caused complaints about cost, queueing and whether the payment should be treated as voluntary, making the launch part of the token's history rather than evidence of an ongoing holder benefit.

The Foundation's governance page says a fee switch could convert protocol fees to ZRO and burn them, but lists the June 2026 vote as Off. Its buyback page separately lists Stargate Revenue as Active. Neither page establishes that ZRO is equity, a guaranteed revenue share, a reserve claim, or ownership of Stargate or LayerZero Labs.

The evidence reviewed supports a live LayerZero interoperability product and Stargate as a live associated product. Etherscan shows the Ethereum ZRO token contract as source-verified and displays active token transfers and LayerZero Endpoint V2 interactions.

LayerZero's June 2026 token article describes Zero as a Layer 1 that will launch and uses future-tense language such as 'When Zero launches.' Zero may be an important roadmap thesis, but it should not be written as an already operating chain or as a current ZRO utility unless a verified launch and contract evidence establish that change.

The V2 whitepaper says the OApp Security Stack is modifiable exclusively by the OApp owner, while current DVN documentation explains required and optional verifier thresholds. This can let an application change providers when a DVN fails, but it also means users must inspect the particular OApp's configuration and delegate/admin arrangements.

The token contract itself is a separate surface from the messaging endpoints. Etherscan identifies a LayerZeroToken contract with ownership-related ABI functions and cross-chain peer/configuration functions; the current owner and live configuration should be checked on-chain rather than inferred from branding.