Open the source-chain explorer for the balance you intend to move and copy its token address before setting up a Super Bridge transfer. The chain and address identify the asset you hold; its ticker and icon do not.
- Identify the Source TokenRead the token address from your wallet’s balance or a recent transfer on the source-chain explorer, then inspect that address on the explorer. Check the full address and network, rather than relying on the abbreviated address your wallet displays. If the balance came from an earlier bridge, identify the token you actually received, not the one you expected to receive.Record the right identifier for the asset type:ERC-20 token: the token contract on that specific EVM chain.Native gas asset: the chain’s native asset, which has no ERC-20 contract.Solana token: the mint address, not your wallet’s associated token account.A token’s symbol, decimals and verified explorer badge can help flag a mistake, but none proves who issued it. A convincing counterfeit can copy the first two, while an explorer’s verified code badge says that published code matches deployed code.
- Which Destination Contract Do You Need?Get the destination token address from the issuer’s published chain-specific records or from the receiving application’s deposit specification. Confirm the mainnet, the full address and the asset representation it accepts. On EVM chains, compare the token’s proxy address when it uses a proxy; its implementation address is not the token your wallet receives.For example, moving Ethereum USDC to Base requires a separate check of the Base output. Circle-issued USDC on Base uses 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913; the older bridged representation, USDbC, is a different asset. Both may trade near one dollar, but an application expecting native USDC may not accept USDbC.
- Match Both Sides in Super BridgeSelect the source and destination networks, then search for each token by its full address where available. Open each token’s details and compare its address with the two addresses you recorded; matching symbols are insufficient. For a native gas asset, check that the selection is the chain’s native asset rather than a wrapped ERC-20 with a similar name.Keep the chain attached to every address in your notes. Ethereum mainnet and Base use chain IDs 1 and 8453 respectively, and an address copied from one network does not establish token identity on the other. If the intended token is absent, stop that pairing instead of selecting a lookalike: available tokens depend on the routes that support them.
- What Will This Route Deliver?Compare routes against the required destination asset before comparing their quoted returns. Super Bridge brings together native bridges and third-party providers so you can compare the transfer paths for your selected pair. In the Superbridge app, check the destination token details again if changing routes or switching between a bridge and a cross-chain swap changes the quoted output.The route mechanism matters: one USDC path can burn source-chain USDC and mint issuer-native USDC after an attestation, while another can lock funds and release a bridged representation. A cross-chain swap may add a swap before or after the bridge, so a familiar ticker in the quote is not evidence of the final contract. Check the recipient as well; a token contract address belongs in the asset field, never the recipient field.Then compare net amount received, network fees, provider fees, estimated time and transaction count. Superbridge fees depend on the selected provider and network transactions; a route with a lower stated provider fee can still deliver less after swap pricing or require a later transaction. For swaps, inspect minimum received and max slippage: the usual default is 0.5% where the setting applies, and a tighter limit can cause a failed transaction when prices move.
- Submit the selected transfer. Refresh an expired quote and confirm that the wallet request still shows the intended source token, amount and spender. An ERC-20 approval authorizes a spender to move that token; an exact-amount allowance limits exposure but can require another approval on your next run.Keep enough native asset for source gas and any manual destination step shown in the route. After signing, retain the source transaction hash so you can distinguish a pending bridge step from a failed start transaction.
- Reconcile the Delivered TokenInspect the destination-chain explorer when the transfer shows complete, and compare the token address in the recipient’s transfer record with your recorded destination address. If the explorer shows the right token but the wallet does not, import that token address into the wallet on the destination network. If the route requires a later finalize transaction, complete it before expecting a destination balance.For repeated transfers, keep a small chain-and-address record for assets you accept, but recheck it when an issuer migrates a token or your receiving application changes its requirements. Choose a route only when its final chain and token address match what the recipient accepts and its net output, time and required transactions meet your needs.