One coin, many networks

Here is the fact that surprises almost everyone once: a coin is not the same thing as the network it travels on. Take USDT, the most traded stablecoin. The same dollar-pegged token exists on Ethereum as an ERC-20 token, on Tron as TRC-20, on BNB Smart Chain as BEP-20, and on several other networks besides. Each version represents the same dollar of value — but they live on entirely separate ledgers that do not talk to each other.

A useful mental model: the asset is the cargo, the network is the railway, and the railways use different gauges. A USDT token on Tron cannot roll onto Ethereum’s tracks. When you send crypto, you are not just choosing what to send — you are choosing which railway it travels on, and the receiving station has to be on the same line.

Why the same coin lives in several places

Token issuers deploy their asset on multiple networks for the same reason a retailer opens stores in multiple cities: that is where the customers are. Each network has its own community, its own applications, and its own fee market. The issuer guarantees that every token, on every supported network, is redeemable for the same underlying value — which is why your exchange balance just says USDT, while the deposit and withdrawal screens ask you to pick a network. The balance is the cargo; the network choice only matters when the cargo moves.

Fees and speed: why the network choice matters

Every blockchain sells a scarce commodity — space in its blocks — and prices it by demand. Networks differ enormously in capacity and congestion, so moving the identical token can cost wildly different amounts.

• An ERC-20 transfer on Ethereum can cost several dollars, and spikes much higher when the network is busy. You pay for the security and depth of the most established smart-contract network.
• The same transfer as TRC-20 or BEP-20 typically costs cents, and confirms in seconds to a couple of minutes.
• Speed differs too: some networks reach effective finality in seconds, while others want several minutes of confirmations before a transaction is considered settled.

For a $100 transfer, a $5 network fee is a 5% haircut — fifty times what a typical trading fee would be. For a $50,000 transfer, the same $5 is noise, and you might happily pay it for the more battle-tested network. There is no universally correct network, only a correct network for a given amount and purpose.

The wrong-network mistake, anatomized

The classic error: your exchange deposit address is set to receive USDT on one network, and you send USDT on another. What happens next depends on an unfortunate detail — several major networks are technically related and share the same address format. An address beginning with 0x is valid on Ethereum and on BEP-20 chains alike, so the sending wallet sees nothing wrong, the transaction confirms, and the funds arrive at the right address on the wrong railway, where nobody is checking the platform.

Blockchain transactions cannot be reversed, recalled, or disputed. There is no payment processor to phone. If the receiving platform controls the address on the other network too, recovery may be possible — typically as a slow, manual, sometimes fee-bearing favor, never as a guarantee. If the address on that network belongs to no one, or to someone else, the funds are simply gone. Between mutually incompatible address formats the transfer usually fails before sending, which is the kinder failure; the dangerous case is precisely the one where everything appears to work.

Memos and tags: the second address field

A handful of networks add a wrinkle: exchanges receive everyone’s deposits at one shared address and tell customers apart by an extra identifier — called a memo, tag, or similar. On those networks, the memo is not optional metadata; it is the part of the address that names you. Send without it and your funds arrive in the shared wallet with no label, which means a support ticket, a wait, and no certainty. If the deposit screen shows a memo field, treat it with the same respect as the address itself.

A pre-flight routine that takes thirty seconds

1. Confirm the asset and the network on the receiving platform’s deposit screen.
2. Select exactly that network in the sending wallet — never assume a default.
3. Copy and paste the address; never type it. Then verify the first four and last four characters after pasting, because malware that swaps clipboard contents for an attacker’s address is a real thing.
4. Include the memo or tag if one is shown.
5. Send a small test amount first. When it lands, send the rest using the same verified details.

Key takeaways

• The same asset can exist on many networks — USDT on ERC-20, TRC-20 and BEP-20 is the canonical example — and those ledgers do not interoperate.
• Fees and speed vary by network because each chain prices its own block space; cents on one railway can be dollars on another.
• Related networks share address formats, so a wrong-network transfer can look perfectly valid while going somewhere nobody is watching.
• Blockchain transfers are irreversible; recovery after a network mismatch is a favor at best, not a right.
• Match the network on both ends, copy-paste and verify addresses, include memos, and always send a test amount first.