Portal Bridge moves supported crypto between blockchains, with routes that differ in the token you receive, the cost, and the wait. For a Portal Bridge cross-chain transfer, Portal Bridge shows available routes and expected output before you sign. Choose by the token your receiving app accepts, then compare total cost.
A blockchain is a separate network; an exchange hides much of the transfer process. From your wallet, you choose both networks and pay transaction fees, called gas. Make sure the destination wallet supports the token.
Portal Bridge Offers Native USDC Transfers
Native USDC transfers work when both networks support Circle's Cross-Chain Transfer Protocol (CCTP). Native means Circle-issued USDC on the receiving chain, rather than a bridge-made copy. If a lending app asks for native USDC, that distinction decides the route.
CCTP destroys USDC on the sending chain and issues new USDC on the receiving chain. A relayer, a service that completes the second transaction, can finish it for you. Manual transfers need gas on both chains; automatic transfers charge for delivery.
Say you hold 100 USDC on Ethereum and want USDC on Base. I would check for native USDC in the quote, then compare the amount received. Automatic delivery can add roughly 0.3 to 5 USDC, depending on the destination; source gas costs extra.
If that route is missing, check both networks and the exact USDC contract, its on-chain identity. Tokens can share a ticker without being interchangeable. Tiny transfers may not cover the delivery fee.
Wrapped Token Transfers Cover More Assets
Wrapped Token Transfers (WTT) lock an original token or burn an existing wrapped one. They then issue or release the destination token. A wrapped token is a claim on the locked asset, with its own contract. The Wormhole Guardian Network signs proof of the source transaction before the destination claim can finish.
This suits assets without a native path and trips back to their original chain. It does not suit an app that accepts only the native asset. Match the receiving app's token contract, not merely the ticker.
Manual transfers need a source transaction and a destination claim. Automatic transfers use a relayer for the claim and charge a fee. Both wait for source-chain finality, when the network treats the transaction as settled; Ethereum can add around 15 minutes.
Keep gas for the source and, if manual, the destination. Some routes offer gas drop-off, turning part of your transfer into the destination's fee token. Check that it covers your next action too.
Fast Swaps Trade Speed Against the Quote
Fast swap routes trade your input for a quoted destination token, sometimes before ordinary chain finality. They suit speed or a different asset, such as ETH on Base from USDC on Ethereum. They fit poorly when the exact token contract matters or the quote is weak.
Some supported routes target under 15 seconds, but the quote is your practical estimate. Compare the amount received, not just the bridge fee. A swap can hide cost in its exchange rate; slippage means the final amount falls below the quote. Check minimum received, quote expiry, and destination gas.
The useful route delivers a token you can spend. Before signing, check four fields:
- Source and destination networks: both must match your wallets.
- Destination token contract: match the receiving app's required asset.
- Net amount and minimum received: include gas, delivery fees, and any swap loss.
- Estimated time and claim step: know if you must finish the transfer yourself.
If the asset is late, use the source transaction hash, its unique receipt number, to track or resume it. For your first wallet transfer, send a small amount before moving the rest.