Guide . Wrong chain

Recovering coins sent to the wrong chain

Sending tokens on the wrong network feels fatal, but for the most common case it isn’t — if you control the destination address, the coins are usually recoverable. Here’s how to tell.

Обновлено в июле 2026 года · KeychainX — Восстановление кошельков с 2017 года

“Wrong chain” usually means you sent tokens over one network to an address that expects another — for example, sending BEP-20 tokens on BNB Chain to an address you use on Ethereum, or moving assets to a network your wallet wasn’t showing. Whether you can get them back comes down to one question: do you control the private key of the destination address?

Why it’s usually recoverable

Ethereum, BNB Chain, Polygon, Avalanche C-Chain, Arbitrum and most other EVM networks all derive addresses the same way from the same private key. That means the same address exists on every EVM chain, and one key controls all of them. So if you sent tokens to your own address but on the “wrong” EVM network, the tokens really are sitting at your address — you just need to view and move them on the correct network. Import that key or seed into a wallet, add the destination network, and the balance appears.

The common scenarios when transfers goes wrong

  • Sent to your own address on the wrong EVM chain. The easy case. Add the network to your wallet (or import the key), and the tokens are there to move. This is the majority of wrong-chain incidents.
  • Sent to an exchange deposit address on the wrong network. Recoverable only if the exchange supports that network and can credit or sweep it. Some will, for a fee; some won’t. It depends entirely on the exchange — contact their support with the transaction hash.
  • Bridged and stuck. If a cross-chain bridge failed mid-transfer, the funds are often recoverable from the bridge contract or by completing the claim — case by case.

When it is NOT recoverable

Some wrong-chain sends really are lost, and it’s important to be honest about which:

  • Sent to a contract address (for example a token contract) that has no way to release the funds — typically unrecoverable.
  • Sent to an address you don’t control — someone else’s address, or a burn address.
  • Non-EVM mismatches — sending an asset to a fundamentally different chain (e.g. a Bitcoin-family address) where your key doesn’t derive the same address.

If the key that controls the destination isn’t yours, or the destination is a contract that can’t send funds back, no service can recover it — and anyone claiming otherwise is not being straight with you.

How we help

Where recovery is possible, the work is about safely deriving and using the right key on the right network — especially when the original wallet was a hardware device, an old seed, or a partially remembered key. We help you locate the funds on the correct chain, confirm the balance, and move it, without you having to expose your seed to any website. If your case is the “own address, wrong EVM chain” type, it’s often quick; if it involves an exchange or a bridge, we’ll tell you honestly what the realistic path is. A common example: someone withdraws a token as BEP-20 on BNB Chain to an address they only ever used on Ethereum. Nothing shows up in their Ethereum wallet, so they assume it’s gone — but the balance is sitting at the exact same address on BNB Chain, and adding that network (or importing the key into a wallet that supports it) makes it appear and spendable in minutes. The coins were never lost; they were simply being viewed on the wrong network.

What to send us to check your case

Diagnosing a wrong-chain send takes three things: the transaction hash, the destination address, and which network the tokens were actually sent on versus where you expected them. With those, the outcome is usually clear within minutes: whether the destination is an address you control or a contract, whether both chains are EVM-compatible, and therefore whether the funds can simply be moved on the correct network or are genuinely stuck. Sending that information up front means we can tell you honestly and quickly whether there’s a real path back, before anyone spends time or money on it.

Avoiding it next time

Two habits prevent almost every wrong-chain loss: always confirm the network (not just the address) before sending, since the same address is valid on many chains; and send a small test amount first when moving between networks or to a new destination. A minute of checking beats a recovery case.

Часто задаваемые вопросы

I sent tokens to my own address on the wrong network — are they lost?

Usually not. On EVM chains the same address and key work across networks, so the tokens are at your address on the network you sent to. Add that network to your wallet (or import the key) and move them.

I sent tokens to an exchange on the wrong chain — can I get them back?

Sometimes. It depends on whether the exchange supports that network and can credit or sweep the deposit. Contact their support with the transaction hash; some recover it for a fee.

I sent tokens to a contract address — is that recoverable?

Usually not. If the destination is a contract with no way to release the funds, they can’t be retrieved. Recovery requires controlling the destination key.

How do I know if my case is recoverable?

The test is whether you control the private key of the destination address, and whether it’s an EVM-compatible chain. If both are true, it’s very likely recoverable.

Do I need gas on the wrong chain to move my tokens?

Yes — to move tokens off the destination network you need a little of that network’s native coin for gas (for example BNB on BNB Chain). Sending a small amount of it to your address is often the only step needed to free stuck tokens.

How much does wrong-chain recovery cost?

Success-based: a percentage of the recovered value only if we recover the funds, and nothing upfront.

Sent coins to the wrong chain?

Send us the transaction hash and the destination address. We’ll tell you within 24 hours whether it’s recoverable, and you pay only on success.

Связаться с KeychainX →