A successful bridge transfer does not move a token’s identity unchanged. It creates or unlocks the version used on the destination network, so you can have the same ticker in your wallet with a different contract address—and that detail is what makes the funds usable on zkSync.
The road there is simple in principle. A bridge moves assets between Layer 1 (the original blockchain, such as Ethereum) and Layer 2 (a separate network built to process transactions more efficiently). When you deposit an ERC-20 token—an ordinary Ethereum-compatible token—the bridge records the deposit on Layer 1 and makes a corresponding token available on Layer 2. The Layer 2 address is not necessarily the Layer 1 address.
That is why “the token is missing” is often the wrong diagnosis. Your wallet may be connected to Ethereum while the balance is sitting on zkSync. Or it may be connected to zkSync but hiding the destination token because its contract has not been added to the wallet’s token list. If what brought you here is exactly that handoff, the zksync bridge question is really: which network holds the asset, and which token contract does that network recognize?
What this feature is actually good for
The separate destination address is useful because applications on zkSync need a local token contract they can read and transfer. Once the bridge finishes, that version can be used for swaps, liquidity, or payments on zkSync without repeatedly returning to Ethereum. The bridge is therefore a doorway between networks, not a currency exchange. It changes where the asset lives; it does not automatically convert USDC into ETH or choose the best trading price.
For a first transfer, use this order:
- Connect the wallet containing the asset and select zkSync as the destination.
- Confirm the asset, amount, and recipient address. For a test, use a small amount you can afford to troubleshoot.
- After the transaction completes, switch the wallet to zkSync and add the destination token only from a trusted contract source. Then check the balance there.
Keep a little ETH on the destination network for transaction fees. A bridged token balance without gas can leave you unable to make the next transaction, even though the bridge worked perfectly.
The practical rule is short: never identify a bridged asset by its ticker alone. Check the network and contract address first. If both match, the “different token” you see is usually the expected destination version—not a second deposit, and not evidence that the original transfer vanished.