LayerZero Splits Automated From Self-Relayed Messages

On January 29, 2024, LayerZero V2 made automated and self-relayed cross-chain messages two ways to deliver the same verified packet: an Executor submits it automatically, or a user submits it on the destination chain. The release changed the market mechanism by separating execution from verification. LayerZero V1’s Relayer handled both jobs; V2 assigns verification to configurable Decentralized Verifier Networks, or DVNs, while leaving execution permissionless. That distinction matters because delivery can fail without making a forged message valid: the destination Endpoint still checks verification before calling the receiving application.

How does automated cross-chain messaging work?

An automated Executor watches for packets, confirms that the selected DVNs have verified them, and calls the destination Endpoint’s receive function. LayerZero’s current build guide documents an Executor receiving its fee on the source chain before paying to complete delivery on the destination. The operator therefore supplies native gas inventory and operational availability—not token liquidity—and collects an execution fee intended to cover gas, rebalancing and a margin. Destination validators or sequencers receive the underlying gas payment. The Executor takes pricing risk if gas moves before execution and operational risk if its RPC service, signer or inventory fails.

The self-relay option removes a service, not verification

With no configured Executor, a user or application can invoke the receive function after verification and pay destination gas directly. That avoids the automated Executor’s service charge, but requires the relayer to obtain the destination token, track message state and submit a correctly parameterized transaction. There is no protocol-supplied liquidity in either path. If the message moves an asset, liquidity comes from a separate bridge design—such as locked collateral, mint-and-burn accounting or market makers—not from the messenger.

Who bears the cost and risk?

The allocation is clearest when the two routes are separated:

• Automated: The sender pays a source-side quote; the Executor fronts destination gas, manages inventory and keeps any margin after costs.
• Self-relayed: The user or app pays destination gas and bears timing, wallet and transaction-management risk; no Executor earns a delivery fee.
• Both: The application chooses the verification stack, so DVN selection—not the delivery method—governs whether a packet is accepted.

A dashboard labeled Manta Bridge tracks one concrete class of cross-chain transfer, allowlisted ERC-20 movements, but transfer volume alone cannot show whether delivery was automated, manually completed or subsidized. Builders need message-level execution records and fee quotes to compare the routes honestly.

Automation wins for products; self-relaying wins as a fallback

Automated delivery enables one-click transfers, source-chain fee payment and composed actions that execute without asking a user to switch networks. Self-relaying is useful for treasury workflows, low-frequency routes and recovery when an Executor stalls. It also keeps the final submission open, limiting an operator’s ability to censor a verified packet indefinitely.

Our view is that automation is the practical default, while permissionless self-relaying is the feature that makes the default tolerable. The important advance is not cheaper bridging by itself; no public evidence here establishes that. It is the ability to buy convenience without granting the delivery provider authority over message validity. What remains unknown is how concentrated Executor traffic is, how wide fee margins run across volatile gas markets, and how often applications test their manual fallback before an outage.