Portal Bridge usually moves supported tokens between separate networks in two transactions: send and claim. For a Solana-to-Ethereum move, Portal Bridge lets you transfer a supported token to your Ethereum wallet through Wormhole, the message network connecting the chains. Check what your app accepts: you may receive a wrapped copy, which represents the original token.
Check which token will arrive
The receiving app must accept the exact token version delivered on its chain. Say you send 1 ETH from Ethereum to Solana. A standard Wormhole token transfer locks the ETH on Ethereum and creates a wrapped copy on Solana. An app that asks for a different version of ETH may not accept it.
Think of the original token as a coat left at a coat check. The wrapped token is a receipt you can use elsewhere; taking it back to its home chain releases the original. Wormhole’s Guardians, a group that checks cross-chain events, sign a message confirming the send. The destination chain checks that message before creating or releasing tokens. Wormhole explains the sequence in its transfer flow.
The deciding check is the token address, its unique ID on a chain. Two tokens can share a name or symbol without being the same asset. If your destination app names a token address, compare it with the version your route will deliver before sending.
Move the token step by step
A Portal Bridge transfer starts with a supported route and finishes when the token reaches the receiving chain. Work through these steps in order so the destination address, token version, and fees are settled before you sign.
- Identify the token your destination app needs. Check its chain and token address, because a familiar symbol alone does not tell you which version it accepts.
- Prepare a wallet for each chain. Keep enough SOL on Solana or ETH on Ethereum to pay gas, the network charge for transactions you must sign.
- Check that your source token and destination chain form a supported route. A chain being supported does not mean every token can travel to it.
- Review the quoted amount you will receive. Compare any network charge and completion fee with the amount you are moving; a small transfer can cost more than it is worth.
- Set the receiving address on the destination chain. Copy it from the wallet that will use the token, then check its first and last characters before signing.
- Approve token access if your source wallet asks. This gives the bridge contract permission to move the chosen token; read the amount in the request.
- Sign the send transaction and save its transaction ID. The source chain must confirm it before Wormhole can produce the signed message used on the destination.
- Complete the claim if the route calls for it. An automatic route uses a relayer, a service that submits the destination transaction for a fee. A manual route needs you to submit that transaction and pay destination gas.
- Check the destination wallet for the expected token address and amount. If the balance is missing, use the saved source transaction ID to check progress before attempting another send.
Allow for fees and a possible extra wait
The total cost depends on gas on both chains, the route, and any relayer fee. Gas changes with network demand, so use the live quote rather than a fixed price. An automatic route can save you a destination transaction to sign, while a manual route leaves that claim to you.
Transfer time also depends on the source chain’s finality, the point when its transaction is settled. Ethereum finality can take around 20 minutes before a delayed transfer is ready for recovery. A token making its first trip to a destination may also need attestation, a one-time registration of its details there.
Check the receiving token first, then check the route and quote, and keep the source transaction ID. The transfer is done when the expected token appears on the destination chain, ready for the app you chose.