Executors

Executors provide Execution as a Service for omnichain messages, automatically delivering and executing calls on the destination chain according to specific resource settings provided by your OApp directly or via call parameters. Automatic execution abstract away the complexity of managing gas tokens on different networks and invoking contract methods manually, enabling a more seamless crosschain experience.

​

What “Execution” Means

In the LayerZero protocol, execution refers to the invocation of the LayerZero Endpoint methods on the destination chain after a message has been verified:

1. lzReceive(...): Delivers a verified message to the destination OApp, triggering its logic.
2. lzCompose(...): Delivers a composed message (e.g., nested calls) after the initial receive logic has triggered.

Both methods are permissionless on the endpoint contract, meaning anyone can call them once the message has been marked as verified.

​

Executors: Execution as a Service

While you could manually call lzReceive(...) or lzCompose(... ) and pay gas on the destination chain directly, Executors automate this process:

• Quote in Source Token: Executors accept payment in the source chain’s native token and calculate the cost to deliver the destination chain’s gas token based on the instructions provided and a pricefeed formula.
• Automatic Delivery: After verification, the Executor invokes the appropriate endpoint method (lzReceive(...) or lzCompose(...)) with the specified resources and message.
• Native Token Supplier: Executors are responsible for sourcing the native gas token on the destination chain, making them a resource for users needing to convert chain-specific resources.
• Fee for Service: Executors charge a fee for relaying and executing messages.

​

Permissionless Functions

Because the endpoint methods are open, your application remains decentralized and trust-minimized, as any party can run an Executor or call the endpoint directly.

​

Message Options

Use Message Options to pass execution instructions along with your payload. Available options include:

• lzReceiveOption: Specify gas and msg.value when calling lzReceive(...).
• lzComposeOption: Specify gas and msg.value when calling lzCompose(...).
• lzNativeDropOption: Drop a specified amount of native tokens to a receiver on the destination.
• lzOrderedExecutionOption: Enforce nonce-ordered execution of messages.

These options let you fine-tune gas usage and value transfers for each message type. More information can be found under Message Options.

​

Default vs. Custom Executors

Choose the executor strategy that fits your application:

1. Default Executor: Use the out-of-the-box implementation maintained by LayerZero Labs.
2. Custom Executor: Select from third-party Executors or deploy your own variant.
3. Build Your Own: Follow Build Executors to implement a bespoke message Executor.
4. No Executor: Opt out of automated execution entirely; users can manually call lzReceive(...) or lzCompose(...) via LayerZero Scan or a block explorer.

​

Executor concentration: a single point of failure for liveness

Unlike DVNs (which support multi-operator X-of-Y-of-N configurations), an OApp configures exactly one Executor per pathway. Today, every default Executor across every pathway in every preset network configuration is operated by LayerZero Labs. This is a structural concentration. It is not equivalent to the DVN concentration discussed in Security Stack (DVNs) — a compromised Executor cannot forge messages, because verification is independent. But a degraded or compromised Executor can:

• Delay or fail message delivery on every OApp using it as the default.
• Censor specific messages by selectively refusing to call lzReceive / lzCompose.
• Mis-account gas / value delivery, breaking application invariants that depend on msg.value or gasleft() at the destination.

For high-value pathways and pathways with strict liveness requirements, evaluate the alternatives in the list above. The available options:

• Run your own Executor (option 3 above). Strongest liveness guarantee; highest operational overhead.
• Use a third-party Executor (option 2). Reduces LayerZero Labs concentration without requiring you to operate infrastructure.
• Run without an Executor (option 4). Trade automation for trust-minimization. Combine with a self-operated relayer that calls lzReceive directly.

The same considerations that apply to a single-DVN configuration — pre-launch monitoring, governance pause, value caps — also apply to a single-Executor configuration.