Wormhole is moving past basic token bridges, now linking over 45 blockchains for messaging, native token transfers, and multichain governance. This growth brings new questions about security, liquidity, and protocol complexity.
Wormhole has stepped out of the shadow of simple token bridges. The protocol now links more than 45 blockchains, giving developers a toolkit for sending messages, moving native assets, and running governance across networks like Ethereum, Solana, Arbitrum, and Base. This puts Wormhole at the heart of the multichain movement, but it also brings a new set of technical and security headaches that go well beyond moving tokens from one chain to another.
Cross-chain messaging and verification
In February 2022, Wormhole suffered one of the largest bridge exploits in history, with attackers minting around 120,000 unbacked wrapped ETH. Jump Crypto, a major investor, restored the lost funds.
This setup avoids the risks of centralized API relays and lets apps check cross-chain data directly on-chain. But it also means Wormhole's security now depends on the Guardian Network's key management and operations, not just the source and target blockchains. If the Guardians are compromised or can't reach consensus, messages could be delayed or blocked entirely.
Native token transfers and intent-based settlement
Wormhole's Native Token Transfers (NTT) aim to tackle a stubborn problem in multichain systems: liquidity gets split up across networks. Instead of wrapping tokens and creating separate pools everywhere, NTT lets projects move their native tokens across chains while keeping control over supply, permissions, and rate limits. Transfers work by locking or burning tokens on the source chain and minting or unlocking them on the target chain. The NTT Manager oversees this process, and the Guardian Network verifies each step.
Settlement, another key piece, brings in an intent-based model for cross-chain trading. Users don't have to manually bridge and swap assets. Instead, they set their goal-like sending USDC on one chain and getting ETH on another. Third-party Solvers then compete to fill the order. This takes the complexity off the user, but it adds new dependencies on off-chain bidding and solver execution. Wormhole messages handle the on-chain verification.
Multichain governance and protocol complexity
In September 2025, Wormhole launched its W 2.0 upgrade, revising the token unlock schedule: some releases shifted from annual to biweekly tranches, while certain lockup periods were extended. This change reflects evolving governance and tokenomics strategies as the protocol matures.
Not every Wormhole product covers every blockchain in the network. Messaging, NTT, Queries, Settlement, and MultiGov each have their own list of supported networks, and this can change. Berachain, Injective, and Scroll, for example, have been dropped from the protocol at times due to security or maintenance issues. Developers need to check which networks are live for each feature before plugging Wormhole into their apps.
Security, liquidity, and competition
Wormhole's move into a full interoperability stack brings new risks. Security is always shifting: weak spots can show up on the source chain, in message checks, Guardian signatures, or when the target chain acts on a message. Liquidity is still a sticking point, since users need enough assets on each network to make transfers and swaps work. The protocol's intent-based Settlement tries to smooth out liquidity sourcing and execution, but the challenge remains.
The competition isn't letting up. LayerZero, Axelar, and Chainlink CCIP are all building their own cross-chain messaging and asset transfer tools, each with different ways of verifying messages and supporting networks. Wormhole's modular design-splitting up messaging, execution, asset transfer, and governance-could help manage complexity, but it also means more parts to secure and keep running.
Wormhole says its infrastructure now supports over 45 blockchains, covering both EVM and non-EVM networks. This growth matches a wider industry shift toward multichain apps, but it also brings tough choices about how to keep so many systems connected and secure. As reported earlier, the move to proof-based verification is changing how blockchains talk to each other, but every approach comes with its own risks and limits.
Wormhole's tools now reach into stablecoins, real-world assets, DeFi, and institutional digital assets. Recent examples include Ripple's RLUSD and BlackRock's BUIDL, both using Wormhole NTT for multichain launches. The protocol's pitch centers on keeping supply, permissions, and asset states in sync across networks, but split liquidity and governance are still open problems.
The W token isn't used as gas for messaging. Instead, it anchors governance and ecosystem participation. Its value depends on market liquidity, supply, governance activity, and how widely the protocol is adopted across chains. Technical utility and market price don't always move together, so users need to separate the two when looking at W's role.
Wormhole's claim to connect more than 45 blockchains as of 2026 comes with a catch: the list of supported networks isn't set in stone. Security incidents, transaction volume, or maintenance costs can all lead to networks being dropped. This means developers and users have to keep an eye on which networks and features are live at any given time.
Wormhole has grown from a simple bridge into a modular protocol for interoperability. Its layered system-combining messaging, verification, native asset transfers, and intent-based settlement-gives developers and institutions new ways to build multichain apps. But keeping security, liquidity, and governance working across dozens of networks is a tall order. How well Wormhole manages these risks will shape its place in the next phase of cross-chain finance.
The protocol's backbone is the Guardian Network, which verifies cross-chain messages using a 13-of-19 signature rule. This setup is meant to give cryptographic proof that messages are valid, but it also means the system relies on the Guardians' security and ability to reach consensus. If the Guardian Network is breached or stalls, cross-chain transactions could be held up or canceled, affecting everyone who depends on Wormhole for interoperability.