What Is Wormhole? Solana's Cross-Chain Bridge Explained

Wormhole is a cross-chain messaging protocol, originally built to connect Solana with Ethereum, that lets applications pass data and assets between more than 30 different blockchains using a network of independent validators called Guardians who observe and attest to events across chains.

It's one of the most widely used bridging protocols in crypto, but it also suffered one of the largest bridge exploits in history, making it a useful case study in both the utility and the risk of cross-chain infrastructure.

How Wormhole works

At its core, Wormhole isn't only an asset bridge, it's a general message-passing protocol. When something happens on a source chain, such as a user locking tokens in a Wormhole contract, the protocol's off-chain Guardian network observes the event and collectively signs an attestation called a VAA (Verifiable Action Approval).

• A set of independent Guardian nodes, currently numbering 19, monitor connected chains for relevant events.
• Once a supermajority of Guardians (13 of 19) sign off on an observed event, the resulting VAA can be submitted to the destination chain.
• Smart contracts on the destination chain verify the Guardian signatures and execute the corresponding action, such as minting a wrapped asset.

This general messaging design means Wormhole can be used for more than moving tokens, including cross-chain governance votes, NFT transfers, and application-level data.

Wormhole's role connecting Solana to other chains

Solana's smart contract environment is not EVM-compatible, so it can't natively interact with Ethereum or other EVM chains. Wormhole became one of the primary ways to move value into and out of Solana's ecosystem, letting users bring assets like wrapped ETH or stablecoins onto Solana to use in its DeFi applications, and move Solana-native tokens elsewhere.

This matters for anyone comparing throughput and fees across ecosystems, since a chain's usability depends partly on how easily capital can flow in and out of it, a topic covered more broadly in our layer-1 comparison guide.

The 2022 exploit and what it revealed

In February 2022, an attacker exploited a vulnerability in Wormhole's Solana-side smart contract, tricking it into believing a set of Guardian signatures had approved a transaction that was never actually verified. This allowed the attacker to mint 120,000 wrapped ETH on Solana without having deposited genuine ETH as collateral, one of the largest bridge hacks recorded at the time.

The incident was ultimately covered by Wormhole's parent organization refilling the drained funds, but it highlighted the core risk of bridge architecture generally: a bug in the verification logic on either side can undermine the entire system's guarantees, regardless of how the message-passing layer itself is designed. See our general crypto bridges guide for how this risk category applies across bridging protocols.

Guardian network trust assumptions

It's worth being clear-eyed about what "decentralized" means in Wormhole's context. The Guardian network consists of a known, permissioned set of node operators, including well-known crypto infrastructure firms, rather than a fully open and permissionless validator set like a base-layer blockchain's. Users are trusting that a supermajority of these known operators behave honestly and that the underlying contracts are bug-free, a different trust model than the proof of stake security of the chains it connects.

Beyond Solana: Wormhole's broader network

While Wormhole originally connected Solana and Ethereum, it has since expanded to support message passing between more than 30 blockchains, including many major layer-1s and layer-2s. This has positioned it as general-purpose interoperability infrastructure rather than a bridge tied to any single ecosystem, with integrations used by various protocols to enable cross-chain governance, cross-chain lending collateral, and multi-chain token deployments where a single asset can exist natively on several chains with Wormhole coordinating the messaging between them.

Steps to reduce risk when using Wormhole

Since bridges are a frequent target for both technical exploits and phishing, a few practical habits reduce exposure: always initiate a bridge transaction from the official project website rather than a link shared on social media, verify the contract address you're interacting with matches the one published in official documentation, and avoid leaving large amounts of bridged, wrapped assets sitting idle in a bridge contract longer than necessary. Reviewing our guide on common DeFi scams is a useful complement before bridging any significant amount.

Wormhole vs. a native rollup bridge

Factor	Wormhole (cross-ecosystem)	Native rollup bridge (e.g. an L2 to Ethereum)
Trust model	Permissioned Guardian network signatures	Inherits base-layer security via fraud/validity proofs
Chains connected	30+ heterogeneous chains	Typically one L2 to its L1
Historical exploits	Yes, major 2022 hack	Less common, though not risk-free
Use case	Broad, multi-chain interoperability	Primarily asset transfer to/from one L2

Bottom line

Wormhole solves a real problem, letting value and data move between otherwise disconnected chains like Solana and Ethereum, but it does so by introducing a permissioned Guardian network as a trust layer rather than inheriting security natively from the connected chains. Its 2022 exploit is a reminder that any bridge, however widely used, carries smart contract and validator-trust risk on top of the underlying chains it connects. If you use Wormhole or similar protocols, treat bridged funds as carrying additional risk beyond simply holding assets on a single chain, and review our DeFi wallet security guide before moving meaningful amounts.