The same token often lives on several networks — USDT on Ethereum, Tron, BSC and more. If you send it on a different network than the receiving side expects, it usually doesn't arrive and can't be recovered. It's the most common way people lose funds in a swap. The good news: it's entirely avoidable.
Why the funds are lost
Each network is a separate ledger. USDT on Tron and USDT on Ethereum are different tokens on different chains that happen to share a name. Send to an address that only exists on one chain, using another chain, and there's no shared record to credit — the deposit lands nowhere either side controls.
The checks that prevent it
- Match the network end to end. Whatever network the order (or recipient) expects, send on exactly that one.
- Check the address format. An Ethereum address starts 0x…, a Tron address starts T…, a Bitcoin address starts bc1/1/3, Monero starts 4…. A format mismatch is a red flag.
- Read your wallet's network selector before confirming — many wallets default to a network you didn't intend.
- For a large transfer, send a small test amount first, confirm it arrives, then send the rest.
How 0trace reduces the risk
When you create an order, you pick the exact network you're sending from, and the deposit address is generated for that chain. Every pair page shows the network plainly and warns that a wrong-network deposit can't be recovered — so you always know which chain to use before you send.
If it already happened
Recovery depends entirely on the networks and whether anyone controls an address on both — often nobody does, and the funds are gone. Treat prevention as the only reliable step, and open the order chat if you're unsure before sending.
