Published on Sun Aug 23 2026 00:00:00 GMT+0000 (Coordinated Universal Time) by Jacob Cavazos

The blockchain ecosystem has fragmented into dozens of networks, each with its own consensus, liquidity, and user base. Ethereum, Solana, the Cosmos app-chain ecosystem, and a growing set of Layer 2 rollups all operate in isolation. Interoperability protocols exist to bridge these islands, allowing assets and messages to move between chains that share no native trust.

Among the most widely adopted interoperability protocols are LayerZero, Wormhole, and Axelar. Each takes a fundamentally different approach to the same problem: how do you verify that something happened on chain A and act on it on chain B without trusting a centralized intermediary? LayerZero uses an ultra-light node model with an oracle and relayer. Wormhole relies on a set of guardian validators. Axelar builds on the Cosmos Inter-Blockchain Communication (IBC) standard with a proof-of-stake validator set.

This article compares the three protocols across security models, throughput, supported chains, developer experience, and real-world track record. For a broader look at how different bridge architectures work under the hood, see our guide on cross-chain bridge security models.

Why Interoperability Protocols Matter

Every cross-chain interaction requires two things: verification and execution. The destination chain must verify that the source chain event actually occurred, and then it must execute the corresponding action, whether that is minting a wrapped token, calling a contract, or releasing locked collateral.

The challenge is that blockchains cannot natively read each other’s state. Ethereum has no way to know what happened on Solana. This means every interoperability protocol must introduce some external component, a set of watchers, validators, or oracles, that observes the source chain and reports to the destination chain. The security of the entire system depends on who those watchers are, how many there are, how they reach consensus, and what happens if some of them act dishonestly.

This is why interoperability protocol choice matters. The security model determines the trust assumptions, the attack surface, and the failure modes. A protocol that relies on a small set of validators has different risk properties than one that relies on a single oracle, and both differ from one that leverages an existing proof-of-stake network.

LayerZero: Ultra-Light Nodes with Oracle and Relayer

LayerZero takes a minimalist approach to cross-chain communication. Rather than running its own validator set, LayerZero separates the verification and delivery roles into two independent components: an oracle and a relayer.

How LayerZero Works

When a message is sent from chain A to chain B through LayerZero, the protocol relies on two parties. The oracle is responsible for reporting the block header of the source chain to the destination chain. LayerZero uses Chainlink and other decentralized oracle networks for this role. The relayer is responsible for delivering the transaction proofs, the Merkle proofs that demonstrate the message was included in the block.

The key security property is that the oracle and relayer must collude to forge a message. If either one acts honestly, a fraudulent message cannot be delivered. The destination chain’s LayerZero endpoint verifies that the block header provided by the oracle matches the proof provided by the relayer. If they match, the message is accepted.

This is called an ultra-light node (ULN) because the destination chain does not need to verify the entire history of the source chain. It only needs to verify the specific block header and proof relevant to the message being delivered.

LayerZero Security Model

LayerZero’s security rests on the separation of duties. The oracle reports block headers, and the relayer delivers proofs. As long as these two parties do not collude, the system is secure. In practice, LayerZero allows applications to configure which oracle and relayer they use, giving developers flexibility but also responsibility.

A criticism of LayerZero’s early design was that the default configuration relied on a single oracle (Chainlink) and a single relayer (LayerZero Labs), which created a potential centralization point. LayerZero has since introduced additional verification layers, including the DVN (Decentralized Verifier Network) framework, which allows applications to add multiple independent verification sources.

LayerZero Supported Chains and Developer Experience

LayerZero supports over 40 chains, including Ethereum, all major EVM Layer 2s, Solana, and several non-EVM networks. The developer experience is built around the OFT (Omnichain Fungible Token) standard, which allows developers to create tokens that can be transferred across chains with minimal integration work. The SDK and documentation are well-regarded, and the protocol has seen significant adoption among token issuers who want native cross-chain functionality.

Wormhole: Guardian-Based Verification

Wormhole takes a validator-based approach. A set of 19 guardians, each running a full node for every supported chain, observes cross-chain messages and signs them. When two-thirds of the guardians (13 out of 19) sign a message, it is considered verified and can be delivered to the destination chain.

How Wormhole Works

When a user sends a cross-chain message through Wormhole, the message is emitted by a contract on the source chain. The guardians observe this emission, verify it, and produce a VAA (Verified Action Approval), which is a signed payload that the destination chain’s Wormhole contract can verify.

The guardians are responsible for running full nodes for every supported chain. This means each guardian must sync and maintain nodes for Ethereum, Solana, and all other supported networks. The guardian set is permissioned, meaning the operators are known and approved by the Wormhole governance process.

Wormhole Security Model

Wormhole’s security depends on the honesty of its guardian set. The system is secure as long as at least two-thirds of the guardians (13 out of 19) are honest. If 7 or more guardians collude or are compromised, they can sign fraudulent messages and mint unlimited tokens on destination chains.

The guardian set is relatively small at 19 members, which has drawn criticism compared to protocols that leverage larger validator sets. However, Wormhole argues that the guardians are reputable, institutionally backed operators, and that the small set enables faster finality and lower latency than larger validator committees.

The Wormhole Hack of February 2022

Wormhole’s most significant security incident occurred in February 2022, when an attacker exploited a vulnerability in Wormhole’s Solana contract to forge a VAA and mint 120,000 wrapped ETH on Solana without corresponding deposits on Ethereum. The exploit resulted in approximately $326 million in losses and remains one of the largest bridge hacks in crypto history.

The vulnerability was not in the guardian set itself but in the contract code that verified guardian signatures on Solana. The attacker was able to bypass the signature verification and self-sign a message that minted wrapped ETH. This highlights an important distinction: even with a sound consensus model, implementation bugs in the verification contract can undermine the entire system. Wormhole was subsequently acquired by Circle and has since undergone multiple audits and security upgrades.

Wormhole Supported Chains and Developer Experience

Wormhole supports over 30 chains, including EVM networks, Solana, Aptos, Sui, and others. The developer experience centers around the Wormhole SDK and the Token Bridge, which allows developers to wrap and transfer tokens across chains. Wormhole also supports generic message passing, enabling cross-chain contract calls and governance. For users looking to move assets to specific networks, our guide on how to bridge to Base covers the practical steps.

Axelar: Cosmos IBC with Proof-of-Stake

Axelar takes a different architectural approach by building on the Cosmos ecosystem’s Inter-Blockchain Communication (IBC) standard. Axelar operates its own proof-of-stake blockchain, and its validator set is responsible for verifying events across supported chains and routing messages between them.

How Axelar Works

Axelar functions as a routing layer. Gateways are deployed on connected chains, and these gateways serve as entry and exit points for cross-chain messages. When a user sends a message through the Axelar gateway on chain A, Axelar’s validators observe the event and reach consensus on its validity. Once consensus is reached, the message is routed to the gateway on chain B, which executes the corresponding action.

Because Axelar runs its own blockchain with a proof-of-stake consensus mechanism, the security of the network is tied to the total value staked with Axelar validators. The more AXL tokens staked, the more expensive it is to attack the network. This is the same security model used by Cosmos chains that participate in IBC.

Axelar Security Model

Axelar’s security model is fundamentally different from LayerZero and Wormhole. Rather than relying on a small set of guardians or a two-party oracle-relayer split, Axelar leverages a decentralized proof-of-stake validator set. As of 2025, Axelar has dozens of validators, and the security of the network scales with the amount of AXL staked.

The proof-of-stake model means that attacking Axelar requires controlling at least one-third of the staked tokens to halt the network or two-thirds to forge messages. The economic cost of such an attack is theoretically higher than attacking a small guardian set, because the attacker would need to acquire and stake a large amount of AXL, and any attack would slash their stake.

However, Axelar’s security is also dependent on the value of the AXL token. If the token’s market capitalization is low relative to the value of assets bridged through the network, the economic security may be insufficient. This is a general concern with proof-of-stake-based bridges.

Axelar Supported Chains and Developer Experience

Axelar supports over 50 chains, with particularly strong coverage of the Cosmos ecosystem via native IBC. It also supports EVM chains, Solana, and other networks. The developer experience is built around the Axelar General Message Passing (GMP) framework, which allows developers to send both tokens and arbitrary data across chains. Axelar also provides a Satellite bridge for users who want a simple token transfer interface without writing code.

Security Model Comparison

The three protocols make fundamentally different trust assumptions. Understanding these assumptions is critical for choosing the right protocol for a given use case.

Which Security Model Is Strongest?

There is no single answer. LayerZero’s separation of duties is elegant but depends on the specific oracle and relayer configuration chosen by each application. A poorly configured application that uses a single oracle and a single relayer has weaker security than one that uses multiple DVNs.

Wormhole’s guardian model is simpler to reason about but has a smaller trust surface. The 2022 hack demonstrated that even with a sound consensus model, implementation bugs can be catastrophic. Since the hack, Wormhole has significantly improved its security practices.

Axelar’s proof-of-stake model offers the most theoretically robust economic security, but it is dependent on the value of the AXL token. For applications bridging large amounts of value, the ratio of bridged TVL to staked AXL is an important metric to monitor.

Throughput and Latency Comparison

Throughput and latency are important for applications that require fast cross-chain interactions, such as cross-chain swaps or real-time messaging.

LayerZero typically achieves delivery times of 1-2 minutes, depending on the oracle’s finality assumptions for the source chain. Because the oracle must wait for the source chain block to be finalized before reporting the header, the latency is bounded by the source chain’s finality time.

Wormhole is generally faster, with delivery times often under a minute for finalized blocks. The guardian set signs messages quickly once the source chain block is finalized, and the VAA can be delivered to the destination chain immediately.

Axelar’s latency depends on its own block production time plus the finality time of the source and destination chains. In practice, Axelar messages typically take 1-3 minutes, though this can vary based on the chains involved and network congestion.

When to Use Each Protocol

Use LayerZero When

LayerZero is a strong choice for token issuers who want native cross-chain functionality through the OFT standard. It is also well-suited for applications that want fine-grained control over their security configuration, including the ability to add multiple DVNs for additional verification. If your application values flexibility and configurability over a single fixed security model, LayerZero’s approach is appealing.

Use Wormhole When

Wormhole is a good choice for applications that need fast cross-chain delivery and broad chain support, including non-EVM networks like Solana, Aptos, and Sui. The guardian-based model is simpler to integrate than a proof-of-stake bridge, and the Wormhole SDK provides solid tooling for both token transfers and generic message passing. Wormhole is also a reasonable choice for applications that want a battle-tested protocol that has survived a major exploit and invested heavily in security since.

Use Axelar When

Axelar is the best choice for applications that want to integrate with the Cosmos ecosystem and leverage native IBC. It is also appealing for applications that prioritize economic security through proof-of-stake and want a larger, more decentralized validator set. If your application needs to route messages across many chains with a single integration point, Axelar’s routing layer architecture is well-suited.

Risks and Considerations

No interoperability protocol is risk-free. Here are the key risks to consider when choosing among LayerZero, Wormhole, and Axelar.

Implementation Risk

As the Wormhole hack demonstrated, the consensus model is only as secure as the code that implements it. All three protocols have undergone audits, but smart contract bugs remain a risk. Applications should review the audit history and bug bounty programs of any protocol they integrate with.

Centralization Risk

LayerZero’s default configuration and Wormhole’s permissioned guardian set both introduce elements of centralization. While both protocols are working toward greater decentralization, applications should evaluate the current state, not the roadmap.

Economic Security Risk

Axelar’s proof-of-stake model ties security to the AXL token’s value. If the token loses significant value, the economic cost of attacking the network decreases. Applications bridging large amounts of value should monitor the ratio of bridged TVL to staked AXL.

Bridging Fundamentals

Regardless of which protocol you choose, understanding the underlying bridge architecture is essential. Our guide on cross-chain bridge security models covers lock-and-mint, burn-and-mint, and liquidity pool models in depth. For practical guidance on moving assets to specific networks, see our tutorial on how to bridge to Base.

Comparison Summary Table

Frequently Asked Questions

Is LayerZero more secure than Wormhole?

LayerZero and Wormhole use fundamentally different security models, so direct comparison is difficult. LayerZero’s security depends on the oracle and relayer configuration, which is application-specific. Wormhole’s security depends on its 19-guardian set. LayerZero has not suffered a major exploit, while Wormhole lost $326 million in February 2022 due to a contract vulnerability. However, Wormhole has since undergone significant security upgrades. The right choice depends on your specific security requirements and threat model.

What is the difference between IBC and Axelar?

IBC (Inter-Blockchain Communication) is a protocol standard developed in the Cosmos ecosystem that allows chains to communicate directly with each other. Axelar builds on top of IBC concepts but adds a routing layer that connects non-Cosmos chains (like EVM networks) to the IBC ecosystem. Axelar’s own blockchain acts as a bridge between IBC-compatible chains and external networks, using its proof-of-stake validator set for verification.

Can I use multiple interoperability protocols at the same time?

Yes. Many applications integrate multiple protocols to avoid single points of failure. For example, a token might be bridged via LayerZero on some chains and via Wormhole on others. Some applications also use multiple protocols for redundancy, falling back to an alternative if the primary protocol experiences downtime. This multi-protocol approach increases integration complexity but reduces dependency on any single protocol.

What happens if a bridge protocol is hacked?

If a bridge protocol is hacked, the consequences depend on the architecture. In a lock-and-mint model, the attacker can mint unbacked wrapped tokens on destination chains, which become worthless once the exploit is discovered. In a burn-and-mint model, the attacker may be able to burn tokens on one chain without corresponding mints on the other. In all cases, users holding wrapped tokens from the compromised bridge may lose value. This is why some users prefer to use native assets or multiple bridges rather than relying on a single wrapped token.

Which protocol has the lowest fees?

Fee structures vary by chain, message type, and network conditions. LayerZero fees are typically paid in the source chain’s native token and cover oracle and relayer costs. Wormhole fees are generally low but may include additional fees charged by the front-end integrator. Axelar fees include gas for the Axelar chain plus destination chain gas. In practice, fees are often dominated by the destination chain’s gas cost rather than the protocol’s own fees. Users should compare total costs, including gas, for their specific route.

Written by Jacob Cavazos