Manual token imports show bridged balances without moving them

Manual token imports add a token’s contract address to a wallet’s display so you can see a bridged balance already recorded on that network. The import changes what the wallet shows; it does not move tokens, complete a bridge transfer or change who controls them.

A bridge may lock an asset on one chain and mint a corresponding token on another, or use a different design to represent the transfer. The destination token has its own contract address, and its balance is separate from the original asset’s balance on the source chain. For a fuller explanation of lock-and-mint transfers, see fermi swap. The key point here is that the wallet needs the destination network and token contract to display that representation.

What does a manual token import change?

It tells the wallet which token contract to read on the selected network. In a typical EVM-compatible wallet, an ERC-20 token contract keeps balances by address, and the wallet can read the connected account’s balance from it. If the wallet does not list that token automatically, adding the contract lets its interface query and display the balance.

The import is a display setting, not an on-chain transaction. It does not call the bridge, mint tokens, approve a spender or move funds. If the destination contract records a balance for your address, the wallet can show it after you add the right token details. If the contract records no balance, importing it will not create one.

How do you find the right token details?

Confirm the destination network and contract address from a source you trust, such as the bridge interface or a verified block explorer page for that network. Then use the wallet’s add-token or import-token control and provide the contract address. Some wallets fill in the token symbol and decimal precision automatically; others ask you to enter or confirm those fields.

• Match the network to where the bridged token was issued.
• Check the full contract address, not just the displayed name or ticker.
• Confirm the balance appears for the wallet address you expect.

Names and symbols are not unique. Two contracts can use the same ticker while representing different assets, and a token on one network is not interchangeable with a token on another just because their names match. The contract address identifies the token the wallet reads; the network determines which chain’s contract it reads.

Why might a bridged balance still be missing?

A manual import cannot fix a transfer that has not completed or a wallet connected to the wrong network. Check the bridge’s transfer status and the destination transaction before drawing conclusions from the wallet display. The destination token may also use a different contract from another route or bridge that represents the same source asset.

There is a narrow safety check worth making before importing: compare the contract address character by character against the bridge’s official destination details. A lookalike token can copy a name or symbol, and adding it only makes that contract visible. It does not authenticate the asset.

For most readers, the better choice is to use the wallet’s automatic token list when it identifies the verified destination token, then import manually only when the balance exists on-chain but is absent from the interface. That keeps the wallet display useful while preserving the distinction between seeing a token and moving one.