LayerZero

LayerZero is messaging infrastructure that moves data between blockchains, and its defining property is that security is configurable per application. That is the most important thing a user can know about it: there is no single answer to how safe LayerZero is.

Applications choose their own verification

Each application selects which oracles and relayers must agree before a message is accepted. A cautious configuration requires several independent parties; a permissive one requires few. Two applications on the same infrastructure can therefore offer completely different guarantees, and users generally cannot see which they are using.

Why that design exists

Different applications have genuinely different needs: moving a large treasury demands stronger verification than sending a low-value message. Fixed security forces everyone to pay for the strictest requirement. Configurability is a reasonable engineering answer to a real problem, and it moves the decision away from the end user.

Messaging is not the same as bridging

The protocol moves messages; bridges built on it move assets. That distinction matters because a messaging flaw becomes an asset loss only where applications hold funds. It also means the largest historical losses in this category came from asset-holding contracts rather than from message passing itself.

The evidence position

Our bridge comparison records no audit report retrievable at a public address for this protocol, despite it securing several billion dollars across a very wide chain deployment. That is the largest published-evidence gap in that comparison.

What ZRO does

The token governs the protocol and its parameters. It is not required for most messaging, so demand relates to governance rather than to usage volume — an important distinction when assessing what the token captures.