Loading precomputed statistics...
Total Packets
Each packet is usually a single crosschain transaction, rarely a bundle of them
All-Default
Incoming packets validated by falling back to the standard LayerZero validation library and settings.
Default Library
Incoming packets using the default smart contract (library) for validation with default or custom settings
Tracked Library
Incoming packets validated by a library of which we decode the validation settings (config)
Required DVN Combinations
Number of unique DVN contract sets used for validation in the 'required' setup
Chains indexed
All incoming packets and validation configs on 18 EVM chains are indexed
Chains seen
Unique source chains of incoming packets (with known validation settings)
Packet
Packets contain a message payload, source EID and destination EID, source OApp address and destination OApp address
DVN
DVN is largely a misnomer, implying multiple validators where in reality there is always a single smart contract and often validation of a single entity's signature
OApp
Most OApps implement token functions. There is no restriction on what an OApp can be, it just needs to include the standard LayerZero messaging interface
OFT
OFTs are the most widely used type of OApp. OFT can refer to a single token on a single chain or the abstracted set of all tokens of the same type across chains
EID
EIDs are needed because some blockchains use the same chain IDs (e.g. Aptos and Ethereum)
Validation Library
The library can be thought of like a panel of switches, allowing for fine-grained control over validation settings
ULN config
ULN, ReceiveUln302 and library are just other words for this specialized smart contract
DVN Set Threshold
Number of DVNs that must validate incoming packets. Combines required DVNs and optional DVN thresholds (0 and >4 grouped as "Other")
Top Required DVN Combinations
Most common required DVN sets by packet count (top 20)
Packet Volume Over Time
Hourly packet count across entire time range
Configuration Changes Over Time
Hourly config changes • — total config changes
Packets by Destination Chain
Local EID distribution
Packets by Source Chain
Source EID distribution
Fragility of Scale
Since you are still here, i invite you to contemplate our motivation for building distributed systems and my motivation for building this website. Some of these systems aim to disintermediate, remove single points of failure, and enhance resilience through decentralization. LayerZero does the opposite by distributing their points of failure. Each added node or edge makes the network more fragile. The protocol fundamentally cannot scale without compromising its security.
LayerZero is by far not the only nor the worst offender among the interop protocols. It is built transparently enough to allow for a monitor like this one that hints at the magnitude of risk. Many competing interop protocols do not provide this onchain transparency. But the existence of more robust, more transparent and more scalable solutions shows that interop can actually be built, and scale, well.
Scroll further to get an intuition for LayerZero's Fragility of Scale.
