Portal Bridge Common Questions

A handy reference for anyone transferring tokens across chains using the Portal Bridge platform. You can also visit the about page for background on the protocol.

What is Portal Bridge and what does it actually do?

Portal Bridge is a cross-chain bridge protocol. It enables you to move tokens — USDC, ETH, SOL, and dozens of others — between blockchains without relying on a centralised exchange. The protocol currently supports more than 30 networks, including Ethereum, Solana, Sui, Base, Arbitrum, Polygon, and Avalanche.

The technology underneath is Wormhole, a message-passing layer that verifies cross-chain transfers through a network of 19 guardians. Every transfer generates a signed attestation before tokens are released on the destination chain. This differs from a custodial bridge: the protocol never holds your assets in a company wallet.

Which blockchains does Portal Bridge support?

More than 30 networks at the time of writing. The most commonly used ones are Ethereum mainnet, Solana, Sui, Base, Arbitrum One, Optimism, Polygon, Avalanche C-Chain, BNB Chain, and Fantom. Cosmos-based chains — including Osmosis and Injective — are also accessible through the Wormhole Gateway.

The list expands as Wormhole adds guardian support for new chains. You can check the current set inside the Portal Bridge swap interface by opening either the source or destination chain selector.

How do I bridge tokens using Portal Bridge?

Connect your source-chain wallet, select a token and amount, choose a destination chain, then connect a receiving wallet for that chain. The interface displays a route and fee estimate before you sign anything.

Once you approve the transaction on the source chain, Wormhole guardians observe it and produce a signed VAA (Verified Action Approval). The Portal Bridge platform then submits that VAA to the destination chain to release your tokens. Most routes complete within two minutes, though Ethereum finality can stretch that to around 15 minutes on congested days.

If the destination transaction does not auto-complete, the interface offers a manual redemption flow — you enter the transaction hash and the protocol resubmits the VAA.

What are the fees for using Portal Bridge?

Fees consist of two parts: the source-chain gas cost and a relayer fee that covers destination-chain gas. The relayer fee is taken from the transferred amount, so you receive slightly less than you send — the interface always shows the expected output before you confirm.

There is no additional protocol fee charged by Portal Bridge itself on standard routes. USDC transfers through Circle's Cross-Chain Transfer Protocol (CCTP) are typically cheaper than wrapped-asset routes because no liquidity pool is involved.

Is Portal Bridge safe? Has it been audited?

The Wormhole core contracts have undergone multiple independent security audits, including by Neodyme and Trail of Bits. Audit reports are publicly available in the Wormhole GitHub repository. The guardian network — 19 nodes run by entities such as Jump Crypto, Certus One, and others — provides the consensus layer that validates every cross-chain message.

That said, no bridge is entirely risk-free. The Wormhole bridge suffered a $320 million exploit in February 2022 caused by a signature verification flaw; the contract was patched and Jump Crypto reimbursed the affected funds. The protocol has operated without a comparable incident since. As with any on-chain activity, you should bridge only amounts you can afford to lose, and independently verify contract addresses.

What tokens can I bridge with Portal Bridge?

Over 100 tokens are natively listed in the interface. These include USDC, USDT, ETH, wBTC, SOL, SUI, MATIC, AVAX, BNB, DAI, tBTC, INJ, and many long-tail assets. The protocol also supports arbitrary token bridging through the generic token bridge, which wraps any ERC-20 or SPL token into a Wormhole-attested wrapped asset on the destination chain.

USDC transfers on supported routes use Circle's CCTP directly, which means you receive native USDC rather than a wrapped variant — a meaningful distinction for DeFi use on platforms like Aave.

Can I use Portal Bridge if I only have a Solana wallet?

Yes. The Portal Bridge interface supports Solana wallets (Phantom, Backpack, Solflare, and others) as the source. You can send SPL tokens from Solana to any supported destination chain. If the destination is an EVM chain, you will need a compatible wallet there — MetaMask or any WalletConnect-compatible option works.

The dual-wallet model (one wallet per side) is intentional: it avoids the complexity of managing multi-chain wallet signatures within a single session.

Why did my transfer take longer than expected?

Several factors can slow a transfer. Ethereum mainnet requires roughly 15 confirmations before Wormhole guardians sign the VAA; at 12 seconds per block that is approximately 3 minutes at minimum, and longer during high-congestion periods. Solana is faster — typically under 30 seconds to finality.

If the relayer fails to auto-redeem, the transaction status page will show a "Redeem manually" option. Enter the source transaction hash into the Portal Bridge interface and it will reconstruct the redemption call. Transfers do not expire; a VAA remains valid indefinitely.

What is the difference between a wrapped token and a native token on Portal Bridge?

A wrapped token is a synthetic representation. When you bridge ETH from Ethereum to Solana via the generic token bridge, you receive Wormhole-wrapped ETH (whETH) — an SPL token backed 1:1 by locked ETH on Ethereum. It is not the same as native ETH on Solana, and not every Solana protocol accepts it.

Native tokens, by contrast, are the canonical asset on their home chain. USDC bridged via CCTP arrives as native USDC on the destination — the kind that Aave, Uniswap, and other protocols treat as first-class collateral. Where a native route is available, Portal Bridge uses it automatically.

How does Portal Bridge handle failed or stuck transactions?

The most frequent failure mode is a relayer that does not auto-submit the VAA on the destination. Your source-chain transaction is already confirmed and your tokens are locked; they are not lost. Go to the transaction history in the Portal Bridge interface, locate the pending transfer, and click "Resume" or "Redeem." You will pay destination-chain gas yourself in this scenario.

If the source transaction itself failed (for example, insufficient gas), nothing was locked — your tokens remained in your wallet. Always check the source chain's block explorer before assuming the worst.

Why should I use Portal Bridge instead of a centralised exchange?

Three practical reasons. First, you retain custody throughout — tokens travel from your wallet to your wallet with no exchange account required. Second, you can bridge assets that centralised exchanges do not support, including long-tail tokens or newly launched SPL tokens. Third, there are no KYC requirements or withdrawal limits.

The trade-off is that you are responsible for gas fees on both chains and for understanding the destination wallet setup. If you are comfortable with self-custody, the Portal Bridge platform is typically faster than a CEX withdraw-then-deposit cycle for the same pair.

You can read more about how the protocol fits into the broader cross-chain landscape on the Portal Bridge about page.

Does Portal Bridge support bridging to Sui?

Yes. Sui is a fully supported chain on the Portal Bridge platform. You can send USDC, ETH, and several other assets to a Sui wallet address directly from the interface. Sui's object model means the receiving address must be a valid Sui wallet — standard 0x... Ethereum addresses do not work here.

Wormhole added native Sui support in 2023 following the mainnet launch. Transfer times to Sui are generally fast given the chain's parallel execution model.

What happens to my tokens if the Wormhole guardian network goes offline?

Your locked tokens on the source chain remain safe — the locking contract does not release them without a valid VAA, so they cannot be stolen by a network outage. The risk is that you cannot complete the transfer until guardians are back online.

The guardian set requires a two-thirds supermajority (13 of 19) to sign a VAA. A temporary outage of several nodes would not halt the network; a coordinated failure of more than 6 nodes would pause new transfers. Historical uptime of the guardian network since 2021 has been very high, with no prolonged outage on record.

Can I bridge NFTs with Portal Bridge?

The underlying Wormhole protocol supports NFT bridging. The Portal Bridge interface — the consumer-facing swap UI — focuses on fungible tokens. For NFT bridging you would typically interact with Wormhole's NFT bridge contracts directly or use a front-end built specifically for that purpose.

Refer to the official Wormhole documentation for the current state of NFT bridge support and any limitations on metadata preservation across chains.

Where can I track my transfer after submitting it?

The Portal Bridge interface shows a live status view after you submit a transaction. Each step — source confirmation, guardian signing, destination redemption — is displayed with a status indicator. You can also paste the source transaction hash into Wormholescan to view the raw VAA status and guardian signatures independently of the Portal Bridge front-end.

For chain-level confirmation, the source and destination block explorers (Etherscan, Solscan, Suiscan, etc.) are the authoritative record. The Portal Bridge UI transaction history also persists across sessions if you reconnect the same wallet.

Looking for general information about the protocol? Visit the about page.

Return to Portal Bridge