103 · Private key creation · lesson 4 of 4
Sending Bitcoin safely — the right address, on the right network
Sending is the one moment your coins are in motion, so it’s the moment worth slowing down for. Two habits stop almost everything that goes wrong — and a third check makes sure your Bitcoin leaves on the real Bitcoin network.
When you send Bitcoin, you type in a destination and approve the payment. That sounds routine, and it usually is. But Bitcoin payments cannot be reversed once they confirm, so a slip here is permanent. The good news: the risks are well understood, and each one has a plain, repeatable defence. Learn them once and sending becomes second nature.
A quick vocabulary note before we start. An address is the string of letters and numbers that says where your Bitcoin should go — think of it like an account number for a single payment. A network is the system your Bitcoin travels over; the real Bitcoin network is the one you want, and there are look-alikes. A hardware wallet is a small dedicated device that holds your keys and has its own little screen. Everything below builds on those three ideas.
The golden rule: verify the address on the hardware wallet’s own screen
Here's why this matters. There is a common type of malware that watches your clipboard. The moment you copy a Bitcoin address, it silently swaps in the attacker's address instead. The one you pasted looks almost identical, so you don't notice, and your coins go to a stranger. Your computer screen can lie to you. Your hardware wallet cannot — it shows the exact address it is about to send to, no matter what the computer claims.
So the habit is simple: when your hardware wallet displays the destination, read it against the address the recipient actually gave you. Check the first few characters and the last few characters, and for a large amount, read the whole thing. Only then press approve. This one step defeats clipboard malware and a compromised computer in a single motion. Never skip it for convenience — it is the step doing most of the work.
Do a small test send first
Send a small test payment, wait for it to arrive, and confirm the recipient actually received it. Then send the rest. Yes, you pay one extra transaction fee for the test — a small price for certainty when real money is on the line. This catches typos, a wrong address, and a swapped address before the bulk of your coins are committed. Bitcoin payments cannot be reversed once they confirm, so a two-step send turns an irreversible mistake into a cheap, recoverable one.
This habit is doing double duty. Modern “bc1” addresses have a built-in typo check that catches almost any mistyped character before it can send — but that check cannot catch the wrong-network mistake covered below, because an address on the wrong network is perfectly valid there. A small test send is what catches it instead. Don’t rely on luck; rely on the test.
How fees work, in plain terms
Fees rise and fall with how busy the network is, a bit like surge pricing. If you're in a hurry, pay the higher suggested rate and your payment settles quickly. If you're not, you can pick a lower rate, or simply wait for a calmer time — fees are often lower on quiet evenings and weekends — and pay less. Your wallet will suggest rates for fast, normal, and slow. For everyday sends, the normal option is fine. There's no need to overpay, and no need to panic if a low-fee send takes a while.
What "change" is, so a big balance doesn't surprise you
Your wallet sends that change to a fresh address that it also controls — one that belongs to you. This is normal and automatic. The only reason to know about it: if you glance at a raw transaction and see a large amount going to an unfamiliar address, don't panic. That's very likely your own change coming back to you, not coins leaving. Modern wallets track this for you, so your balance stays correct. You just never want to mistake your own change address for a mystery payment and second-guess a good transaction.
Learn to glance at an address so a wrong one looks wrong
A real Bitcoin address today starts with “bc1” (older ones start with a “1” or a “3”, and those still work). If the address your wallet shows starts with “0x”, stop — that is an Ethereum-family address, not Bitcoin, and it’s the fingerprint of the wrong-network trap covered next: your coins heading for a copy of Bitcoin instead of the real one. Your real Bitcoin wallet will only ever give you a “bc1” (or 1/3) address to receive at, so if an exchange is willing to send “Bitcoin” to a “0x” address, that’s the moment to back out. Match the shape: real Bitcoin goes to a real Bitcoin address.
There is only one real Bitcoin — the confusion is all the copies
This matters for one reason: those copies use a different kind of address and a different network. If you send “Bitcoin” out as one of these copies, it lands on that other network — and your ordinary Bitcoin wallet, which only watches the real Bitcoin network, will show nothing. The money isn’t destroyed, but it’s sitting on a road your wallet doesn’t drive on. For a beginner, that usually means it’s gone or a painful support-ticket recovery at best. The fix is simply to never use the copies: only ever send real, native Bitcoin.
The one screen that traps people: the “network” menu
You want the option that means the real Bitcoin network. It’s usually labeled “Bitcoin,” and sometimes “BTC,” “Bitcoin network,” “On-chain,” “Native SegWit,” or “SegWit.” All of those mean the same thing: normal Bitcoin. What you do not want, unless you specifically know otherwise, is anything that says BEP-20, ERC-20, BSC, or a network name that isn’t Bitcoin — those send one of the copies described above.
So the rule at that screen is calm and simple: choose “Bitcoin.” If you’re withdrawing to a hardware wallet or a phone wallet you set up for Bitcoin, “Bitcoin” is always the right answer.
Lightning is real Bitcoin — but it’s a different door
In practice that means: a Lightning payment uses a special one-time invoice (a long code often starting with “lnbc,” or a QR code), while an on-chain payment uses a normal “bc1” address. Don’t paste a Lightning invoice into an ordinary send, or a “bc1” address into a Lightning send — use the one the receiver asked for. This isn’t dangerous the way the stand-in copies are; a mismatched Lightning payment usually just fails or bounces back rather than vanishing. But knowing they’re two different doors saves confusion. When you’re moving savings into cold storage, you want plain on-chain Bitcoin — the “bc1” kind.
Put it together: your first withdrawal
- Generate a fresh receive address in your wallet app. Modern wallets offer a new one every time — take it.
- Verify that address on the hardware wallet’s own screen, not just on the computer. It’s the same golden rule as sending: the little screen is the one display malware can’t touch.
- In the exchange’s withdrawal form, make sure the network is Bitcoin — never BEP-20, ERC-20, or any other lookalike. This is the menu from the section above.
- Send a small test amount first. Coffee money, not savings.
- Wait for it to arrive — which means confirmed. Your wallet will show the payment almost immediately as unconfirmed: the network has seen it but not yet locked it in. It counts as arrived once it’s confirmed — written into the ledger — which typically takes ten minutes to an hour. Wait for at least one confirmation.
- Then send the rest — a fresh address again, checked on the device screen again.
Read the address on the hardware wallet’s own screen, and send a small test first. Malware can change what your computer shows you; it cannot change what that little screen shows you. And a test send turns an irreversible mistake into a cheap one. At any “network” menu, the answer is always Bitcoin.
- Verify the destination address on the hardware wallet’s own screen, not just on your computer or phone.
- For a new address or a large amount, send a small test payment first and confirm it arrived.
- Only ever send real, native Bitcoin — never a wrapped copy like “BTC (BEP-20)” or “Wrapped Bitcoin.”
- At an exchange’s “Network” menu, choose “Bitcoin” (also shown as BTC, on-chain, SegWit, or Native SegWit).
- Check the address shape: real Bitcoin starts with “bc1” (or 1/3). A “0x” address is not Bitcoin — back out.
- Keep Lightning and ordinary on-chain sends separate: use the exact invoice or address the receiver gave you.
- Pick a fee that matches your urgency — higher for fast, lower if you can wait for a calmer time.
- Expect “change” to come back to one of your own addresses; a large amount to an unfamiliar address is usually your own change.
Check yourself
2 questions on what this lesson just covered. Nothing is scored, recorded or saved — it isn’t sent anywhere and it’s gone when you close the tab.
1You copy an address, paste it into your wallet software, and it looks right on your computer screen. Is that enough to approve the payment?
Address-swapping malware watches your clipboard and quietly substitutes an attacker’s address — and it can show you the address you expected while doing it. Checking on the computer therefore proves nothing, because the computer is the compromised part. The hardware wallet’s own small screen cannot be faked that way: read the address there, confirm it matches where you meant to send, and only then approve. Every single time, not just for large amounts.
2You are moving a meaningful amount to a wallet you have never sent to before. What do you do first?
A test send proves the address, the network, and your receiving wallet all work, for the price of a few cents in fees. Splitting the amount into equal chunks feels safer but proves nothing: if the address is wrong, every chunk goes to the same wrong place. Send a little, confirm it arrived and that you can see it in the destination wallet, then send the rest.
✓ Last verified: August 4, 2026