Before signing, ask the recipient to confirm the asset, network and full address. Check any extra destination fields, fees and amount received. For a new destination, start with a small test and wait for receipt.
Asset, network and address
Read the whole string
Balance and fees
Confirm the destination
Get deposit instructions directly from the recipient. The same token may exist on networks that are not interchangeable. For a service, check the networks it actually supports and any additional destination fields.
Inspect the address
Copy the address from a trusted source, then compare it in full in the wallet or on the signing device. An address taken from transaction history or matching only its first and last characters may be a trap.
Budget the costs
Check the amount sent, provider withdrawal fees and the native asset needed for network fees. If the recipient needs an exact amount, account for all costs before confirming.
Make a test
For a first transfer or large amount, send a small sum on the same network to the same destination. Confirm receipt with the recipient before sending the rest. The test also incurs a fee.
Track the outcome
Keep the transaction identifier. Check its status on an explorer for the correct network and distinguish broadcast, inclusion and service credit. If it remains pending, follow the wallet’s official procedure instead of blindly resending the amount.
Diagnose a pending transfer
“Processing” at a platform can precede any onchain broadcast. With a hash, inspect the correct network, transaction status and destination; without one, first ask the provider whether withdrawal was sent.
- Chain confirmation does not prove the recipient has credited its account yet.
- Do not send a second transfer to “unlock” the first without diagnosing it.
Practical case: decision and limits
A test succeeds, then a new address is supplied for the main amount. The test does not cover that change: repeat recipient, network and asset checks. An exchange may require a tag or memo despite a correct address. Copy from the official source and compare the entire address; history may contain an attacker’s lookalike.
A concrete verification
Get the address from the official source: unsolicited transfers can insert lookalikes into history.
Checks to make
| Topic | Check |
|---|---|
| Confirm the destination | Asset, network and address |
| Inspect the address | Read the whole string |
| Budget the costs | Balance and fees |
| Make a test | Try a new route |
| Track the outcome | Hash and receipt |
Frequently asked questions
Does the same 0x address work on every network?
Not necessarily. A matching address format does not mean the recipient accepts the selected network or token.
Does a small test guarantee the next transfer?
No. It reduces some destination errors, but recheck the details and network state for every send.
What if I selected the wrong network?
Stop further sends and contact the recipient or service through its official channel. Any possible recovery depends on custody and supported networks.
What if an unknown token arrives unsolicited?
Receipt alone generally does not require your signature. Do not open its description URL or sell it to unlock a claimed reward. Names, displayed values and unsolicited transfers establish neither legitimacy nor liquidity.
Verifiable sources
Independent educational content reviewed against primary documentation. No personalized recommendation or promise of returns. Updated October 6, 2026
