Sent Crypto on the Wrong Network: What Should You Check First?

Stop sending and copy the transaction hash. “Wrong network” can describe several different incidents: a rejected withdrawal, a failed transaction, tokens at your own address on another EVM chain, an unsupported exchange deposit or funds sent through the wrong bridge route. Recovery depends first on where the transaction exists and who controls the destination keys.

Do not create a second incident

Do not send gas, a verification payment or another copy of the transfer. Do not follow a direct-message recovery link. A second transaction cannot relabel the first and may create another loss.

Find the transaction hash before naming the problem

Open the sending wallet or exchange history and copy the transaction hash. Record the asset, selected network, amount, destination, time and withdrawal status. If no hash exists, the sender may not have broadcast the transaction and its support team remains the first contact.

Branch 1: the transaction failed

A failed on-chain transaction usually means the token did not move, although a network fee may have been consumed. Confirm the status on the explorer for the selected network. The next action is fixing gas, balance or contract conditions—not asking the receiver to recover funds it never received.

Branch 2: the destination address was invalid

Some sending systems reject an address whose format does not fit the selected chain. If the withdrawal was rejected before broadcast, funds should remain with the sender. If a transaction succeeded, the destination was valid under that chain’s rules even if it was not the address you intended.

Branch 3: you control the destination keys

When tokens were sent to your own EVM address on another EVM-compatible chain, the same seed or private key may control that address on both networks. Add the correct network and verified token contract to a trusted wallet interface. You will need the native gas asset of the chain to move the token. Never enter the seed phrase into a website that claims to reveal the missing balance.

Branch 4: an exchange controls the address

An unsupported exchange deposit cannot be repaired from your wallet. The exchange decides whether its custody system can access the token, identify your account and perform a manual credit or return. Recovery may be unavailable, delayed or more expensive than the deposit.

Branch 5: a smart contract or bridge controls the destination

Tokens sent to a contract can be recoverable only if the contract has a supported rescue or refund path and the operator can invoke it. A bridge transaction also has a source-chain event, message state and destination-chain result. Use the official bridge explorer and support process; do not call arbitrary contracts suggested in social media.

Similar addresses do not merge blockchains

A matching 0x string can exist on Ethereum, Base, BNB Smart Chain, Polygon and other EVM networks. The assets remain on the chain where the transaction was mined. The controlling key may be the same in self-custody, but a custodian can monitor and credit only selected routes.

Gather a minimum recovery packet

Support needs facts, not a description such as “my coins disappeared.”

• Transaction hash
• Actual blockchain used
• Asset and token contract
• Amount
• Destination address
• Sender and receiver platform names
• Expected blockchain
• Transaction status and timestamp
• Memo or tag if applicable
• Screenshot of the receiving instruction

Identify the only party that can move the funds

The relevant party is the holder of the destination key or contract authority. In self-custody, that may be you. For an exchange address, it is the exchange. For a bridge contract, it is the protocol under its documented rules. A blockchain explorer can locate the balance but cannot transfer it.

Do not confuse unsupported with unconfirmed

An unconfirmed transaction may simply need more blocks or may be replaced. A confirmed transfer on an unsupported network has completed on-chain but is not recognized by the destination’s account system. These cases require different support questions.

Do not bridge funds you no longer control

A bridge can move tokens only from an address or contract that can authorize the source-chain transaction. If an exchange now controls the destination address, you cannot bridge the balance from outside. Sending gas to that address does not grant control.

Assess whether manual recovery is economical

Kraken currently documents case-dependent recovery fees and states that recovery is not guaranteed. Other exchanges can decline unsupported deposits entirely. Compare the official fee and expected effort with the value of the asset. Do not pay an unofficial agent to recover a balance that only the custodian controls.

Worked example: token sent to your own EVM address

A user sends a token on BNB Smart Chain to the same 0x address used in an Ethereum wallet. The explorer shows success and the user controls the seed. The balance can often be viewed by adding BNB Smart Chain and the legitimate token contract, then moved with BNB for gas. This path does not apply when the address belongs to an exchange.

Worked example: unsupported exchange deposit

A user sends USDC on Polygon to an exchange that accepted USDC only on Ethereum. The Polygon explorer shows the deposit address received the token. The user cannot import the exchange address or bridge the funds. The correct path is one complete unsupported-deposit ticket.

A safe support request

State the actual and expected networks, include the transaction hash and ask whether the exact asset-network combination is eligible for manual credit or return. Ask about the official fee before approving action. Keep all communication inside the provider’s authenticated support channel.

When recovery is unlikely

Recovery can fail when nobody controls the destination key, the token contract is fraudulent, the custodian does not support the chain operationally, the contract has no rescue path or the value is below the recovery threshold. Blockchain immutability means no general authority can undo a valid transfer.

Current conclusion

The first question is not whether two networks look compatible. It is where the transaction settled and who controls the destination. Use the hash, classify custody and contact only that controlling party.

Research boundaries

Exchange guidance was used to establish that unsupported-network recovery is provider-specific and not guaranteed. The self-custody branch is limited to cases where the user genuinely controls the relevant key. No private recovery service is endorsed.

Recovery documentation reviewed — July 28, 2026

Official exchange, issuer and blockchain documentation was prioritized.

• Coinbase Exchange network warning: https://help.coinbase.com/en/exchange/crypto-transfers/depositing-to-coinbase-exchange
• Kraken crypto deposit recovery: https://support.kraken.com/articles/crypto-assets-deposit-recovery
• Tether token recovery policy: https://tether.to/en/tether-token-recoveries/
• Circle supported currencies and blockchains: https://developers.circle.com/digital-asset-accounts/references/supported-currencies-and-blockchains
• TRON resource model: https://developers.tron.network/docs/resource-model

FAQ