The Cost of Being Wrong About a Network
Sending an asset on a network the recipient does not support is the most expensive routine error in crypto. What is recoverable and what is not.
The same asset exists on many networks with the same name and ticker. Choosing the wrong one on a withdrawal is the single most common expensive mistake, ahead of typos by a wide margin.
Why it happens
The network selector is a dropdown, frequently pre-filled with a default, positioned away from the address field where attention is focused.
The address format is often identical across networks, so nothing about the address indicates which network it belongs to.
The result is an interface where the most consequential field is the least prominent.
The four cases
Case one: your own wallet, same address on both networks. Common on EVM-compatible chains, where one private key controls the same address everywhere. The funds are on a network your wallet is not currently displaying. Add the network in settings and they appear.
Fully recoverable, and this is the most common case.
Case two: a venue, wrong network. The venue was not watching that network for your deposit. Many have a recovery process, sometimes with a fee, taking weeks. Contact support with the transaction hash immediately.
Frequently recoverable and slow.
Case three: a non-EVM chain. Sending to an address format that does not correspond to a key you control on that chain. Generally unrecoverable.
Case four: a contract address that cannot forward tokens. Recoverable only if the contract has a rescue function and someone with permission uses it. Usually neither.
The prevention
Check the network before the address. Reversing the usual order of attention addresses the problem directly.
Confirm what the destination supports. Before withdrawing, check which networks the receiving wallet or venue accepts for that specific asset. Support differs by asset, not just by venue.
Send a test transaction. Ten dollars, confirm arrival, then send the rest. This catches every case above while the amount at risk is trivial.
Use the cheapest network both ends support, which is usually a rollup, and confirm rather than assume.
The information you need in advance
Which networks your venue supports for withdrawal, per asset. Which networks your wallet supports, per asset.
Both are published. Venues listing per-asset network support alongside fees, such as an exchange with a published withdrawal schedule, make the check a single page rather than an investigation.
If it has happened
Get the transaction hash. Look up the destination on an explorer for the network you actually used.
If it is your own address, add the network to your wallet. If it is a venue, open a support ticket immediately with the hash, the asset, the network and the timestamp. Speed affects whether recovery is possible.
Do not post publicly asking for help, which attracts fraudulent support accounts within minutes.
Fees move with network demand. Any figure here reflects the date shown above and should be re-checked before you act on it. Where a measurement was taken by hand, the article says so.
Related reports
- How to Read a Fee Estimate Before You Confirmtransaction troubleshooting
- The Cost of Dusttransaction troubleshooting
- Failed Transactions: Why You Still Pay for Themtransaction troubleshooting