What is LayerZero V2?
LayerZero V2 is not a classic lock-and-mint bridge but an omnichain messaging protocol. Applications and tokens use it to pass messages and value between chains, with security handled by configurable verifier networks rather than a single pooled vault. Its token standard lets assets exist natively across many chains instead of being wrapped in one place.
Reach and measured data
Reach is its headline strength: our data shows LayerZero V2 spanning 91 chains, the widest in this bridge set, and we measured a fast 58 ms endpoint latency. About $7.2B in value is associated with it. Despite that scale, its overall score is 5.65, ranking 8th of 15, held back by two factors below.
Why the score is mixed
Our review did not credit audits within scope and found no public status page. That does not mean the protocol is unaudited in reality, only that our automated scan did not capture qualifying audits. The deeper point is architectural: messaging protocols move trust to whoever configures and runs the verifier and executor roles for a given app. A misconfigured integration, not the core protocol, is often where cross-chain value is lost. Interoperability layers are a repeated target for attackers, and losses across the bridge sector have run into the hundreds of millions in single incidents.
Who is it for?
- Good fit: Builders and users who need the broadest chain coverage and understand configurable security.
- Poor fit: Users who want a simple, single-vault bridge with a published status page and clear audit trail in one place.
Because security depends heavily on each application's configuration, evaluate the specific integration you are using, not just the protocol name.
How to evaluate an integration
Since the protocol pushes security decisions to the application layer, the practical checklist is application-specific: which verifiers secure the route you are using, whether the token is a native omnichain asset or a wrapped representation, and how much value the specific pathway already carries. Two apps built on the same protocol can have very different safety profiles. Our numbers describe reach, latency and value at a point in time and do not capture per-integration configuration, which is where most cross-chain losses originate. Size positions accordingly, and prefer well-established, heavily used routes over novel ones until they have accumulated a track record.