Skip to content
Last updated 2026-11-05

Sent on the Wrong Network?

A transaction exists only on the chain that recorded it. This page helps you identify that chain and choose a recovery path. It cannot promise that a confirmed transfer is recoverable.

Who this is for

You approved a transfer on a chain other than the one the recipient expected, or a deposit has not arrived. Skip this page if the recipient can already see the funds on the right network.

Before you start

  • The transaction hash from the extension's activity list.
  • The network shown for that transaction, and the network the recipient requires.
  • The destination address, copied in full.
  • A rule: never send more funds to unlock or verify a transfer, and never share the recovery phrase with anyone offering to recover it.

Steps

1. Read the network on the transaction

Open the extension's activity and select the transaction. The details name the network and show the chain ID. A transaction is recorded only on the chain that processed it, so the Bitgold explorer cannot see a transfer made elsewhere.

2. Check the hash on the right explorer

For Bitgold, open www.bitgold.live and paste the hash. For another EVM chain, use that chain's explorer. If the hash is not found, check that you copied all of it and that the explorer matches the network in the details.

3. Switch networks before assuming the worst

Use the extension's network selector to switch to the destination chain. If it is not listed, add it with the official parameters. The same address can exist on several EVM chains, so the funds may be sitting on another ledger rather than gone.

The extension and the Binance app keep separate network lists. A network added in one client does not appear in the other until you add it there.

4. Match the case to a recovery path

  • You control the destination address: restore the same wallet in a client that supports the destination chain, add the network, and check the balance. Bridging back to Bitgold costs fees and adds risk.
  • The destination is an exchange deposit address: contact the exchange with the hash, chain, amount, and deposit address. Only the exchange can credit or return the deposit.
  • The destination is non-EVM: the extension's custom networks are EVM-only. Recovery to an address on Bitcoin, TRON, or Solana is usually impossible.
  • Nobody controls the destination: if it is a burn address or a contract with no withdrawal function, recovery is usually impossible.

5. Keep a record

Save the hash, the explorer link, and any support ticket number. Do not delete the wallet; it still controls the sending address.

Verify it worked

Recovery worked only when one of these is true:

  • The destination address shows the expected balance on the destination chain's explorer.
  • A bridge or exchange transfer back to Bitgold confirms and the BTG arrives at an address you control.
  • The exchange confirms in writing that it will credit the deposit.

A chat message is not confirmation. Use the exchange's own support portal.

Troubleshooting

Problem What to do
The recipient sees nothing Give them the hash and network name. For an exchange deposit, open a ticket instead of messaging a "support" account.
The explorer does not find the hash You may be on the wrong explorer or using a partial hash. Match the explorer to the network in the extension.
The network is missing from the selector Add it with the official parameters; the extension supports EVM custom networks only.
You sent to your own address on another chain Restore the same wallet in a client for that chain, add the network, and check the balance.
Someone offers to recover the funds for a fee Decline. A confirmed transfer cannot be reversed by a third party.

Next steps