Match the Token’s Network Before Sending It to an Exchange

To move tokens to an exchange, send them on a network that the exchange supports for that specific deposit asset. A wallet address alone does not identify the route: the network determines where the transaction is recorded, while the token contract or native asset identifies what is being transferred. The exchange credits a deposit only after it detects a supported asset on a supported network and satisfies its deposit rules.

How do I check which network an exchange requires?

Open the deposit page for the exact asset and select a network listed as available for deposits. Exchanges can support the same ticker on several networks, but support for one does not imply support for another. Read the network name and any displayed token or contract details, then compare them with the withdrawal options in the wallet or service holding your tokens. The network chosen at both ends must refer to the same chain.

Do not infer network compatibility from an address format. Many EVM networks use addresses with the same format, so an address that looks valid can still receive a transaction on the wrong chain. The exchange may not monitor that chain for deposits, or it may be unable to credit the transfer through its normal process. Likewise, a familiar ticker can refer to distinct assets on different chains. If the exchange publishes a token contract for the selected network, compare it with the asset details shown by your sending wallet.

Some networks also require a memo, tag or destination identifier in addition to the address. The exchange deposit page specifies whether one is required. Enter it in the corresponding field in the sending interface; putting it into the address field can change the destination and cause a failed or uncredited deposit.

What if my tokens are on a different network?

If the exchange does not accept deposits on the network where your tokens currently reside, the tokens need to reach a supported network before you send them to the deposit address. One route is to withdraw or bridge them to a network the exchange accepts, then make a separate exchange deposit from that network. A bridge transfer has its own source transaction and destination-side completion; the exchange deposit is a later transaction with separate network and asset requirements.

A bridge may deliver a wrapped representation of an asset, or another token issued for use on the destination network. That representation is not automatically the same deposit asset the exchange lists. Check the resulting asset and network against the exchange’s deposit page before sending. For a fuller account of bridge completion and recovery, see this guide to Wormhole bridge transfer recovery. A pending bridge message or incomplete destination transfer does not count as an exchange deposit.

Alternatively, if you control the tokens in a self-custody wallet, you may be able to use a service that supports both the current network and a network accepted by the exchange. Compare the asset it will deliver, the destination network, and the final withdrawal or transfer route. A route with fewer conversions can reduce contract and fee exposure, but availability and costs depend on the particular asset and networks.

How do I send the deposit and confirm it arrived?

Once the asset is on a supported network, copy the deposit address from the exchange’s page for that same asset and network. Confirm any required memo or tag, and check that the sending interface identifies the expected network and token. If the exchange assigns a different address for each network, use the address shown after selecting the intended network; do not reuse an address from another asset’s deposit page.

Before sending a full balance, check the network fee and the amount that will arrive after any service fee. A small test transfer can help confirm that the exchange recognizes the route, though it may be uneconomical where fees are high or the exchange has a minimum deposit. Keep the transaction ID. It identifies the on-chain transfer and can help support staff trace it, but it does not itself prove the exchange has credited the account.

• Confirm the exchange enables deposits for the asset and selected network.
• Match the sending network to the network named on the deposit page.
• Verify the token or wrapped asset and enter any required memo or tag.
• Check the transaction on the relevant chain, then check the exchange deposit status.

After the chain records the transaction, the exchange may wait for its required confirmations or perform additional processing before crediting the balance. A transaction can therefore be successful on-chain while still pending in the exchange account. If the network, asset or destination identifier was wrong, stop before sending more. Recovery depends on whether the exchange controls the destination and supports recovery for that particular chain and asset; it is not guaranteed.