Portal Bridge is a cross-chain token bridge that moves supported tokens between two blockchains, including Solana and Ethereum, through Wormhole. If your tokens are in your own wallet, Portal Bridge lets you transfer them to another supported chain. You choose the receiving wallet and cover the network costs yourself.
What changes when you bridge from your own wallet?
Portal Bridge lets you send a supported token from a wallet on one chain to a wallet on another. When you withdraw from a centralised exchange, the exchange handles the transfer and decides which networks it offers. With a bridge, you hold the token before sending it and approve the transaction from your own wallet.
That control gives you a different job. You must choose the source chain where your token actually sits, the destination chain where you want to use it, and a recipient address on that destination. An Ethereum address and a Solana address are different kinds of addresses; copying the wrong one is not a detail the bridge can fix after you send.
A bridge also does not necessarily give you the same form of a token that an exchange would send in a withdrawal. It moves value through a cross-chain route, often by issuing a wrapped representation on the destination. Before sending, identify the exact token the recipient or intended app accepts, rather than relying on a familiar symbol alone.
How does the transfer work?
A Wormhole Wrapped Token Transfers route records an action on the source chain and completes a matching action on the destination chain. If you send a token from its home chain, the token bridge locks it there. Wormhole’s Guardians observe the source transaction and sign a message called a VAA, which proves the transfer details to the destination chain.
When that signed message is submitted on the destination chain, its token bridge verifies it and mints a wrapped token for the recipient. On a return trip, the wrapped tokens are burned and the locked originals are released. The tokens are not travelling through a shared account: each blockchain records its own transaction, with the signed message connecting the two.
Completion may involve a relayer submitting the destination transaction, or it may require you to claim the tokens with a destination-chain transaction. That distinction matters when you budget for gas and decide when the transfer is finished. A confirmed send on the source chain proves the first leg happened; check the destination transaction or wallet balance before treating the transfer as complete.
Which asset will arrive?
The asset you receive depends on the token’s home chain and the route, so check its identity before you send. In a Portal Bridge Solana to Ethereum transfer, a Solana-origin token sent through a wrapped-token route would arrive as its Wormhole-wrapped representation on Ethereum. Its name may resemble another token’s, but its contract identifies what you actually hold.
Consider the reverse direction with Wrapped Ether (WETH). Send WETH from Ethereum to Solana through that route, and the receiving wallet gets a Wormhole-wrapped version on Solana. Send that wrapped asset back through the corresponding route, and it is burned so the original WETH can be released on Ethereum. The outward transfer creates a representation; the return transfer restores the asset held by the bridge.
This is the check that decides whether a transfer serves your purpose: will the destination wallet or app accept that specific asset? A matching ticker is insufficient. Check the destination token’s identity and route before approving, especially if you intend to use it in an app rather than simply hold it. On Wrapped Token Transfers routes, amounts are also normalised to eight decimal places; avoid entering finer precision when the exact amount matters.
What will it cost, and how long will it take?
Portal Bridge transfer fees depend on the chains, token and completion method, so there is no single fee to apply to every transfer. You need the source chain’s native token for its transaction fee. An ERC-20 token may also require a separate approval transaction the first time you use it. A manual claim needs destination-chain gas, while a relayed transfer may deduct a relayer charge from the amount received.
For a small transfer, compare the amount expected at the destination with the source gas and any claim or relay cost before signing. A route that saves you a destination transaction can still cost more in tokens received. Keep some native token available in your destination wallet if you expect to claim manually or use the arrived asset afterward.
Portal Bridge transfer time is governed partly by source-chain confirmation. Wormhole lists roughly 14 seconds for Solana finality and roughly 19 minutes for finalised Ethereum transactions; these are chain benchmarks, not promised end-to-end times. Guardian attestation, relaying or a manual claim, and destination confirmation add to the wait. If the source transaction has confirmed but the asset has not arrived, check whether the destination leg still needs completion before starting another transfer.
How do you make your first transfer and know it worked?
Start with a small amount you can identify easily in both wallets. Have the token in your source wallet, the correct recipient address, and enough native token for the transactions you may need to sign. Then check these four details together before you approve anything:
- Source: the chain and token your wallet currently holds.
- Destination: the receiving chain, address and exact asset expected there.
- Amount: what you are sending and what the route says should arrive after any charges.
- Completion: whether a relayer handles the destination leg or you must claim it and pay gas.
Approve the source transaction only after those details match your intention. Save its transaction record, then follow the transfer through to the destination transaction. If the token does not appear in a wallet’s default view, check the destination transaction and the token’s contract before assuming it failed; a wrapped asset may need to be displayed separately.
Once the small transfer is complete, confirm that the receiving wallet holds the asset your next app accepts. You now have the information needed for a larger transfer: the actual destination token, the costs shown for your route, and whether completion requires action from you. Make that check again for each new token or chain pair.
Top comments (0)