- The Wormhole bridge connects over 30 blockchains — including Ethereum, Solana, Avalanche, and Sui — letting you move ERC-20 tokens across ecosystems without a centralized exchange.
- Bridging uses a lock-and-mint model: your original token is locked in a smart contract while a wrapped version is minted on the destination chain.
- 19 independent validators called Guardians must agree before any cross-chain transfer is approved, using a 13-of-19 threshold.
- You need native gas tokens on both your source and destination chains before you start — skipping this step strands your tokens.
- Always test with a small amount first and navigate to the Portal directly — phishing clones of the bridge UI are common.
- Developers can integrate Wormhole’s TypeScript SDK or embed the Wormhole Connect widget into any dApp with minimal code.
The Wormhole bridge is a cross-chain protocol that lets you move ERC-20 tokens from Ethereum to 30+ other blockchains in minutes. You lock tokens on the source chain, a network of validators verifies the action, and wrapped tokens appear in your wallet on the destination chain. This wormhole bridge tutorial covers every step from wallet setup to receiving your tokens — and what developers need to know to build with the protocol.
What Is the Wormhole Bridge?
Wormhole launched in October 2020 as the first token bridge between Ethereum and Solana.[1] Since then it has grown into a full cross-chain messaging platform supporting over 30 networks including Ethereum, Solana, Avalanche, BNB Chain, Polygon, Arbitrum, Base, Sui, and Aptos.[2] By April 2025, the protocol had processed more than $59 billion in all-time transfer volume and surpassed one billion cross-chain messages, placing it first industry-wide on both metrics.[1]
The protocol does not move assets directly. Instead, it deploys a lightweight smart contract on every connected chain and uses a network of 19 trusted validator nodes — called Guardians — to observe events on a source chain and produce a cryptographic proof called a Verified Action Approval (VAA).[3] Independent relayers then carry that proof to the destination chain, where the local smart contract verifies the signatures and releases or mints your tokens. Separating verification from execution is what makes Wormhole fast and chain-agnostic.
How Wormhole Guardians Work
The Guardian network is Wormhole’s security foundation. It runs on a Proof-of-Authority (PoA) model: 19 known validator companies — not anonymous actors — each hold an equal stake in the multisig. To approve any transfer, at least 13 of those 19 Guardians must independently observe the same on-chain event and sign the same message hash.[3] That signed package becomes your VAA.
A VAA (Verified Action Approval) is the only key that unlocks your funds on the destination chain — no VAA means no transfer. Each Guardian runs full nodes for every connected chain simultaneously, watching Core Contract logs in real time. When 13 of 19 sign the same message, the resulting VAA is submitted to the destination chain’s contract, which checks the signatures, confirms it has not seen that VAA before, and then mints or releases your tokens.[4]
Lock-and-Mint vs. Native Token Transfers
Most ERC-20 transfers through the Portal use a lock-and-mint mechanism. Your original token is deposited into an escrow smart contract on Ethereum, and an equivalent wrapped token is minted on the destination chain.[5] To get your original token back, you burn the wrapped version and the escrow releases it on Ethereum. This is why tokens bridged via Wormhole often carry names like “wETH” or “wSOL” — they are wrapped representations of the original asset.
Wormhole also offers a newer standard called Native Token Transfers (NTT) that lets token projects maintain a single unified supply across multiple chains. Rather than locking assets and creating a wrapped copy, NTT burns tokens on the source chain and mints them natively on the destination chain, preserving a consistent circulating supply.[5] In September 2024, Sky (formerly MakerDAO) used NTT to bring its USDS stablecoin to Solana — allowing DeFi users to move USDS natively between chains without fragmented wrapped versions or separate liquidity pools.[1] For a user just moving an ERC-20 from Ethereum to another chain, the Portal Bridge with its lock-and-mint model is the easiest starting point.
| Your Goal | Best Approach | What You’ll Need |
|---|---|---|
| Move an ERC-20 to another chain (one-off) | Portal Bridge UI at portalbridge.com | MetaMask + native gas on both chains |
| Move assets to/from Solana frequently | Portal Bridge or PancakeSwap Wormhole widget | Phantom wallet + SOL for gas |
| Embed bridging inside your dApp | Wormhole Connect widget | npm + React app + minimal config |
| Build custom cross-chain logic | Wormhole TypeScript SDK | npm install @wormhole-foundation/sdk |
| Transfer tokens natively (unified supply) | Native Token Transfers (NTT) | Token issuer integration required |
Wormhole Bridge Tutorial: Step-by-Step for ERC-20 Tokens
This wormhole bridge tutorial walks through the Portal Bridge — Wormhole’s primary end-user interface available at portalbridge.com.[6] The same core flow applies to integrated UIs like PancakeSwap’s Wormhole widget, because they all run the same underlying protocol. Before you begin, confirm you have:
- MetaMask (or another EVM-compatible wallet) installed and funded with the ERC-20 you want to bridge, plus ETH for gas.
- A destination-chain wallet installed (e.g., Phantom for Solana, or MetaMask on a second network) with enough native tokens to cover the redeem transaction. This is the step most beginners miss — if your destination wallet has zero SOL or zero AVAX, you cannot complete the final step.
Step 1 — Open the Portal Bridge and Connect Your Source Wallet
Go to portalbridge.com by typing the URL directly or accessing it from the official Wormhole documentation — never follow a link from an unknown source or social media post. Click “Connect Wallet” in the source panel and choose MetaMask. Approve the connection popup. The UI will now show your Ethereum address and token balances. Before doing anything else, verify the URL in your browser bar. Phishing clones of the Portal Bridge do exist; the real site will never ask for your seed phrase or private key.
Step 2 — Select Your Source Chain, Token, and Amount
In the “From” section, confirm Ethereum is selected as your source chain. Open the token selector and search for the ERC-20 you want to move. Enter the amount you want to bridge. Always leave some ETH in the wallet after setting your amount — you will need gas to pay for both the token approval and the transfer transaction. A safe buffer is at least 0.01 ETH beyond what you are bridging. If this is your first time, start with a small test amount — even $5 worth — to confirm the full flow before moving larger sums.
Step 3 — Select Your Destination Chain and Recipient Address
In the “To” section, choose your target blockchain from the dropdown. Many Portal UIs auto-populate the destination address when you connect a second wallet — for example, connecting Phantom will fill in your Solana address automatically. If you are entering the address manually, double-check it character by character. On-chain transactions cannot be reversed, and sending to a wrong address means permanent loss of funds. Note that Solana addresses look very different from Ethereum addresses — verify the format matches the destination chain before proceeding.
Step 4 — Approve the ERC-20 and Initiate the Transfer
Because ERC-20 tokens require explicit on-chain permission before a smart contract can move them, you will first see an “Approve” button. Click it and confirm the gas transaction in MetaMask. This approval grants the Wormhole Portal Token Bridge contract the right to access that specific token in your wallet. Once the approval confirms on-chain (usually under a minute), click “Transfer” and confirm the second transaction. This deposits your tokens into the Wormhole escrow contract on Ethereum and emits a cross-chain message that the Guardian network begins watching for immediately.[4]
Step 5 — Wait for Guardian Confirmation and the VAA
After your Ethereum transaction confirms, the Portal shows a status screen with a progress indicator. This is where the Guardians get to work. All 19 validator nodes observe your transfer event on Ethereum and each one waits for the required number of block confirmations before signing. Once 13 of the 19 have signed the same message hash, the VAA is produced and is ready to be submitted to the destination chain.[3] For Ethereum, this step typically takes a few minutes because of its block confirmation requirements. Some chains with faster finality — like Solana — clear this step in seconds.
Keep your browser tab open during this step. While the VAA is stored on-chain and can be retrieved later through the WormholeScan explorer[7], staying on the page allows most UIs to automatically trigger the redemption flow as soon as the VAA is ready. Copy your Ethereum transaction hash from MetaMask before anything else — this is your tracking number if you ever need to look up the transfer manually on WormholeScan.
Step 6 — Redeem Your Tokens on the Destination Chain
When the VAA is finalized, the UI prompts you to connect your destination-chain wallet if you have not already done so. Click “Redeem” and approve the transaction in your destination wallet. The destination chain’s Core Contract verifies all 13 Guardian signatures inside the VAA, checks that this VAA has never been used before (replay protection), and then releases your wrapped tokens to your address. After the transaction confirms, your wrapped ERC-20 will appear in your wallet. Add the token contract address to your wallet’s token list if it does not appear automatically — the Portal UI provides the address for you.
“Messaging is the core, most important layer… It’s a way to share state to update in a secure and decentralized way.”
— Robinson Burkey, Co-Founder, Wormhole Foundation[10]
| Feature | Wrapped Token Transfer (Portal) | Native Token Transfer (NTT) |
|---|---|---|
| How it works | Lock on source chain, mint wrapped copy on destination | Burn on source chain, mint native token on destination |
| Token supply impact | Original token stays locked in escrow | Unified circulating supply across all chains |
| What you receive | Wrapped token (e.g., wETH on Solana) | Native token on destination chain |
| DEX swap needed after? | Often yes, to get the canonical version | No — token is already native |
| Best for | Any user doing a one-off ERC-20 transfer | Token projects deploying natively multichain |
Developer Tools: Wormhole SDK and Wormhole Connect
If you are building a dApp and want to add cross-chain transfers without sending users away from your site, Wormhole offers two integration paths that suit different levels of customization.
Wormhole TypeScript SDK
The Wormhole TypeScript SDK gives you programmatic control over the entire bridging flow: selecting chains, building transfer transactions, checking VAA status, and submitting redemptions.[8] Install it with:
npm install @wormhole-foundation/sdk
The SDK abstracts the differences between blockchains so your application code does not need to know whether it is interacting with an EVM chain or Solana. You work through a unified API: define the source chain, destination chain, sender address, token, and amount, and the SDK builds the correct transactions for each network. For miners moving into smart contract development, building with the SDK is the most educational path — you will see exactly what happens at each step of the bridge process and get hands-on experience with cross-chain message flows.
Wormhole Connect
If you want a production-ready bridge widget in your frontend with minimal work, Wormhole Connect is a pre-built React component you can embed in any dApp.[9] It handles wallet connections, chain selection, token approval, the full transfer flow, and the redemption step — all in a polished interface that matches the Portal experience. Configuration is a few lines of JSON specifying which chains and tokens you want to support. This is how integrators like PancakeSwap embed a Wormhole bridge tab directly inside their DEX without building the bridging logic themselves.
Security: What Every User Needs to Know
Cross-chain bridges are high-value targets and Wormhole has its own security history to learn from. In February 2022, an exploit on Solana allowed an attacker to mint 120,000 wETH without backing collateral — the largest bridge hack at the time. Jump Trading, Wormhole’s backer then, replaced the full value of the stolen funds.[2] In the aftermath, Wormhole deployed two critical safeguards: the Global Accountant, which tracks token balances across all chains to prevent unbacked mints, and the Governor, which applies per-chain daily transfer limits so no single chain can drain the system unexpectedly. The bug bounty program was also expanded to $10 million to incentivize responsible disclosure.
For end users, the practical safety checklist is short. Always navigate to bridge URLs by typing them directly or using links from the official Wormhole documentation. Send a small test transfer before moving significant value. Save your Ethereum transaction hash — it is your tracking number on WormholeScan. And always ensure your destination wallet has native gas before you start. There is nothing more frustrating than tokens arriving on a new chain with no gas to do anything with them.
Wormhole and the Chia Ecosystem: A Conceptual Bridge
If you follow Chia Network, the ideas behind Wormhole’s architecture will feel familiar. Chia’s native smart contract language, Chialisp, uses a coin-puzzle model where every coin is locked by a puzzle — essentially a locking script — and spending it requires providing a valid solution. The Wormhole VAA system works on similar logic: a VAA is a cryptographic solution produced by the Guardian network that the destination chain’s smart contract validates before releasing funds. In both cases, the critical question is the same: has a trusted set of parties agreed this action is valid?
Chia is actively developing its own bridge infrastructure. In March 2024, the Chia team announced work on the Chia Bridge — a cross-chain asset transfer system — alongside a HackerOne bug bounty program to harden the protocol’s security before launch.[11] Understanding how Wormhole’s Guardian-based attestation model handles trust, finality, and wrapped asset issuance gives Chia developers a strong mental model for what Chia’s own bridging layer will need to solve when it goes live.
For anyone building in the Chia ecosystem, Wormhole is the clearest live reference for how cross-chain verification works in production at scale.
Conclusion
This wormhole bridge tutorial has walked you through the full lifecycle of moving an ERC-20 across chains: understanding the Guardian network and VAA proofs, preparing wallets and gas on both chains, approving and initiating the transfer on Portal, waiting for the 13-of-19 Guardian signatures, and redeeming your wrapped tokens on the destination chain. The flow is consistent whether you use the Portal UI directly, an integrated widget like PancakeSwap’s, or your own dApp built on the TypeScript SDK. Start with a small test amount, keep your transaction hash handy, and bookmark portalbridge.com directly so you never land on a phishing clone. And if you’re building in the Chia ecosystem, the way Wormhole’s VAA system works is as good a reference as any for the cross-chain trust model Chia’s own bridge will eventually mirror.
Wormhole Bridge Tutorial FAQs
What is a wormhole bridge tutorial?
A wormhole bridge tutorial is a step-by-step guide to moving tokens from one blockchain to another using Wormhole’s Portal Bridge. It walks you through connecting your wallets, approving your ERC-20, initiating the transfer, waiting for Guardian confirmation, and redeeming your wrapped tokens on the destination chain.
How long does a wormhole bridge tutorial transfer actually take?
A typical Ethereum-to-Solana transfer via Wormhole takes five to fifteen minutes from the moment you initiate the transaction to receiving tokens in your destination wallet. Most of that time is the Guardian network waiting for Ethereum’s required block confirmations before the 13-of-19 signatures can be collected and the VAA finalized.
What happens to my ERC-20 when I bridge it with Wormhole?
Your original ERC-20 token is locked inside a Wormhole escrow smart contract on Ethereum while an equivalent wrapped version is minted on the destination chain. To retrieve your original token, you return the wrapped version to the bridge and the escrow contract on Ethereum releases your funds.
Do I need gas on both chains to complete a Wormhole transfer?
Yes — you need ETH on Ethereum to pay for the token approval and the transfer transaction, and native gas tokens on the destination chain (such as SOL on Solana or AVAX on Avalanche) to pay for the redeem transaction. Arriving on a new chain with no native gas is the most common reason users get stuck midway through a bridge.
Is the Wormhole bridge safe to use?
Wormhole has processed over $59 billion in all-time volume and implemented significant security upgrades after its 2022 exploit, including the Global Accountant, the Governor rate-limiter, and a $10 million bug bounty program. No bridge is entirely risk-free, but using the official Portal at portalbridge.com and always testing with a small amount first are the two most effective precautions.
Wormhole Bridge Tutorial Citations
- Wormhole Foundation — Connecting the Internet Economy: Wormhole and the W Token’s Past, Present, and Future
- CoinPaprika — Wormhole Blockchain Bridge: How It Connects 30+ Networks
- Wormhole Docs — Guardians
- Wormhole Docs — VAAs (Verified Action Approvals)
- Messari — Understanding Wormhole: A Comprehensive Overview
- Portal Bridge — Official Bridge UI
- WormholeScan — Wormhole Explorer and Analytics
- Wormhole Docs — Get Started with the TypeScript SDK
- Wormhole Docs — Wormhole Connect Overview
- CryptoNews — Robinson Burkey, Co-Founder of Wormhole, on Bridges and Cross-Chain Communication
- ChiaTribe — Chia News March 2024: Chia Academy, Chia Bridge and HackerOne
