Decentralised News · Last reviewed 21 November 2026 · Reader decision guide
What matters: A correct-looking wallet address is not sufficient. You need the exact asset, chain, full recipient destination, possible memo/tag, fee budget and confirmation policy before transferring any meaningful funds.
Seven-step transfer rehearsal
| Step | Before you proceed | Why it matters |
|---|---|---|
| 1. Identify the receiving service | Check the official deposit screen or independently verified self-custody recipient | Prevents payment to an impostor |
| 2. Match asset and chain | Confirm token, network and supported contract | Same ticker across chains does not mean interchangeable deposits |
| 3. Verify full destination | Compare every character and verify address changes separately | Mitigates address poisoning and clipboard replacement |
| 4. Check memo/tag | Use the exact receiving-platform tag if required | Shared deposit addresses may need customer identifiers |
| 5. Review amount and fees | Check deposit minimum, withdrawal minimum and gas | Tests and large transfers both have nonrecoverable costs |
| 6. Choose a rehearsal | If practical, send a small test amount and confirm recipient credit | Tests operational routing, not all future risks |
| 7. Send and reconcile | Check hash, confirmations, recipient balance and timestamp | Network success differs from custodian posting |
DN Transfer Readiness Gate
Check only items verified from a trusted source. This instrument does not initiate a transaction.
What to do if the recipient does not see the deposit
Start with the transaction hash and the appropriate blockchain explorer. Confirm network success and destination. If the deposit reached the correct exchange address but is not credited, contact the official receiving platform with the hash, network, asset, amount and required memo. If funds went to the wrong address, the network may not support reversal; recovery depends on the actual recipient and platform.
See DN’s address-poisoning prevention guide for a separate public-address comparator.
Sources, limitations and disclosure
Methodology: Guidance uses the primary provider documentation linked above and a DN decision checklist; individual outcomes depend on the asset, blockchain, institution and current product rules. No live deposit or recovery procedure was performed by DN. This is educational information, not financial advice. Provider mentions do not constitute paid rankings and no unverified affiliate links are used.
Frequently asked questions
Is a small test transfer always necessary?
It is a useful precaution for unfamiliar destinations or substantial amounts, but network fees and minimum deposit amounts can make it impractical. A test alone does not guarantee a later transfer.
What if the recipient requires a memo or destination tag?
Use the receiving platform’s exact memo or tag in addition to the address. Missing or incorrect values can prevent automatic crediting and may lead to loss.
Can I recover a transfer sent to the wrong network?
Sometimes, depending on whether the receiving account can control the destination address on that chain and whether the platform supports recovery. Never assume recovery is possible.
What is a transaction hash?
It is a blockchain transaction identifier used to inspect network state. It does not prove a custodial platform credited a specific customer’s account.
When is a transfer final?
Finality varies by network and receiving service. The recipient may wait for additional confirmations or apply compliance checks.
Should I copy the destination from recent transaction history?
No. Address-poisoning attacks deliberately insert lookalike addresses. Obtain the recipient’s current address through a trusted independent channel.
What if the transfer is pending?
Check the explorer and sender wallet’s documented pending-transaction options. A confirmed transfer generally cannot be cancelled.
Can I send any token to a matching-looking address?
No. Token support, chain, contract and destination service compatibility must all match.