Three checks before you send
Address, network, amount. Getting any one of them wrong can mean an irreversible loss. Time spent checking is always cheaper than trying to recover.
- Address: from a trusted source, not a string pasted from a chat.
- Network: confirm the recipient's deposit network matches yours.
- Amount: test with a small amount first, then send the rest.
Five steps
- Get the recipient address. Ask for the address and the network, preferably as a screenshot or copied text rather than typing it by hand.
- Send a test amount. Send the minimum first and wait for confirmation. This filters out most errors.
- Check the address. After pasting, compare the first and last six characters. The middle can be folded; the ends are what you verify.
- Set the fee and submit. Choose a fee for current congestion and confirm the total before submitting.
- Verify. Copy the transaction hash into a block explorer, check the status and confirmations, then tell the recipient.
What a wrong network does
When the same asset exists on several chains, the addresses and networks are not interchangeable. Sending Ethereum-network USDT to an address that only supports Tron usually means the funds are not returned automatically.
| Situation | Result | Recoverable |
|---|---|---|
| Same network, correct address | Arrives normally | — |
| Wrong network | Funds may be stranded at an intermediate address | Depends on whether the recipient supports cross-chain recovery; usually costly and uncertain |
| Malformed address | The network may reject it | If it never reaches the chain, no funds are deducted |
| Valid address nobody controls | Funds are locked permanently | No |
Fees and confirmation speed
A fee buys block space. When the network is busy, the highest bids are included first. Chains price differently: bitcoin by transaction size, Ethereum by computational complexity (gas), and some newer chains use fixed or very low fees.
A practical rule: if you are not in a hurry, pay a lower fee and accept a few hours; if you need speed, raise it. Do not leave a large transfer stuck in the queue to save a few dollars.
Common errors and recovery
- Wrong address: not recoverable once confirmed. If the recipient is an exchange account, contact their support, but success is not guaranteed.
- Wrong network: contact the receiving platform immediately with the transaction hash and ask whether cross-chain recovery is supported.
- Fee too low: use the wallet's "speed up" function where available, or wait for congestion to ease.
- Duplicate submission: do not resend because it is taking a while; check the transaction hash first.
- Malicious approval: revoke unknown approvals immediately in an approval manager, then move remaining assets to a new address.