How to Send Crypto Safely: The Test-Transaction Rule
One wrong character and your funds are gone forever. Here is a repeatable routine for sending crypto without losing it to a typo or a fake address.
Crypto has no undo button. Send funds to the wrong address and there is no bank to call, no chargeback, no support ticket that reverses it. That single fact should change how carefully you press "send," and yet most people paste an address and confirm in seconds.
Quick answer
To send crypto safely, always send a small test transaction first, confirm it arrives, then send the rest. Verify the full destination address, not just the first and last few characters, and confirm you are on the correct network. Prefer a human-readable name like an ENS domain over a raw address when possible, and never copy an address from your transaction history, where scammers plant lookalikes. A minute of checking is cheaper than a permanent loss.
Key takeaways
- Send a test transaction first. A tiny amount confirms the address and network before you commit the full sum.
- Check the whole address, especially the middle, not just the start and end.
- Match the network. Sending on the wrong chain can lose funds even if the address is correct.
- Use ENS or a saved contact to avoid pasting raw hex where a typo is invisible.
- Never reuse an address from your history; address-poisoning scams count on exactly that.
Why one mistake is unrecoverable
A blockchain transaction is final by design. Once it is confirmed, ownership has moved and no central party can pull it back. That is the whole point of self-custody, but it means the burden of getting the details right falls entirely on you.
Three mistakes cause almost all avoidable losses:
- A wrong or altered address, whether from a typo, a clipboard hijacker, or a poisoning scam.
- The wrong network, for example sending an asset on one chain to an address that only controls it on another.
- A confirmation you did not read, where a malicious site swapped the recipient at the last second.
The test-transaction routine defends against all three at once.
The test-transaction routine
- Copy or select the destination address, ideally from a saved contact or by typing an ENS name.
- Confirm the network matches on both ends (same chain, correct token standard).
- Send a small test amount, enough to be visible but small enough that losing it would not hurt.
- Wait for the recipient to confirm it actually arrived at the intended wallet.
- Only then send the full amount, verifying the same address and network again.
Yes, it costs a little extra in fees and a few minutes of patience. Weigh that against the size of the transfer. For a large amount, a test transaction is the single highest-value habit in all of crypto.
Verify the address the right way
Wallets show addresses as long strings of characters, and the human brain is terrible at comparing them. Scammers exploit this. In an address-poisoning attack, they generate a lookalike "vanity" address whose first and last characters match yours, send you a zero-value transaction so it appears in your history, and wait for you to copy the wrong one next time.
So verify like this:
| Check | Weak habit | Safe habit |
|---|---|---|
| Address source | Copy from transaction history | Copy from a saved contact or fresh paste |
| Comparison | Glance at first and last 4 chars | Check the middle characters too |
| Human readability | Raw hex string | ENS name or labeled contact |
| Clipboard | Trust what you pasted | Re-verify after paste, watch for swaps |
We go deeper on the lookalike trap in our address poisoning explainer. The short version: never trust an address just because it is already in your history.
Names beat addresses
An ENS name such as yourname.eth maps a readable label to a wallet address, so instead of comparing 42 hex characters you confirm a word you recognize. Many wallets resolve ENS names natively when sending on Ethereum and compatible chains.
Two cautions keep this safe:
- Confirm the resolved address the first time. A name only helps if it points where you expect, so verify the underlying address once when you save the contact.
- Protect the name itself. ENS names can be phished or hijacked; treat the account controlling your name with the same care as any other valuable asset.
Names reduce typo and poisoning risk dramatically, but they are a convenience layer over an address, not a replacement for verifying it the first time.
Get the network right
A correct address on the wrong network is still a lost transfer. The same-looking address can exist on multiple chains, and a token can follow different standards. Before sending:
- Confirm the asset and its network match on both the sending and receiving side.
- If moving between chains, use a proper route rather than a raw send; our guides on bridging crypto safely and cross-chain intents cover the safer paths.
- When an exchange gives you a deposit address, use the exact network it specifies for that deposit, not a different one that "should also work."
What to do right now
Before your next transfer, especially a large one:
- Save the recipient as a contact or use an ENS name instead of pasting raw hex.
- Send a test amount and wait for confirmation of arrival.
- Verify the middle of the address, not just the ends.
- Double-check the network on both sides.
- Read the final confirmation screen in full before approving, and reject anything that looks altered.
If you are also tightening up account security, pair this with our secure crypto exchange account checklist so both your funds in transit and your accounts are protected.
Frequently asked questions
Is a test transaction really worth the extra fee?
For anything beyond a trivial amount, yes. The fee for a small test is negligible next to the permanent loss of sending the full sum to a wrong or malicious address. Scale the habit to the stakes.
Why should I not copy an address from my transaction history?
Because address-poisoning scammers deliberately plant lookalike addresses there. Copying from history is exactly the behavior they are counting on. Use a saved contact, an ENS name, or a freshly verified paste instead.
What is the most common way people lose funds sending crypto?
Sending to a wrong or altered address, often from a typo, a clipboard hijacker, or a poisoning scam, and sending on the wrong network. The test-transaction routine catches both before you commit the full amount.
Does using ENS make sending completely safe?
It removes the typo and poisoning risk of raw addresses, but you still must verify the underlying address the first time and keep the ENS account itself secure. It is a strong safeguard, not a substitute for care.
This article is for general information and is not financial advice.
