Getting & keeping bitcoin

Ch 9 · Sending Your First Sats

Getting & keeping bitcoin progress: chapter 6 of 9
You chose: Getting & keeping bitcoin

Sending Your First Sats

Hook

Sending bitcoin feels like tapping “Pay” on a card—until you notice there is no chargeback desk and no instant “posted” guarantee. The network moves value when a transaction is built, broadcast, and confirmed. Your first send should teach that rhythm, not chase speed.

One idea

A first send is a small, deliberate practice run: you create a transaction that unlocks some of your bitcoin and locks it to someone else’s address, pay a fee for inclusion, and wait for confirmation—because Bitcoin is not an instant card network.

Plain walkthrough

Start tiny. Use an amount you can afford to mistype—often a few sats (the smallest bitcoin units) or a small test payment to yourself or a trusted destination. This chapter is about the mechanism of sending, not about whether or how much anyone should acquire. Practice with what you already control in a wallet you set up on purpose.

The send screen, step by step.

  1. Paste or scan the destination — an address or invoice from the receiver (Chapter 8). Prefer their QR or a single paste from a trusted channel; then eyeball the start and end of the string.
  2. Enter the amount — in bitcoin or sats, depending on your wallet’s display. Double-check units so “0.001” and “1000 sats” are not confused.
  3. Review the fee — wallets suggest a network fee (paid to miners for including your transaction in a block). Higher fee-rate usually means faster inclusion when the network is busy; lower can mean a longer wait. Chapter 12 goes deeper. For a first send, a normal wallet suggestion is enough.
  4. Confirm on the device — especially on hardware wallets, read the address and amount on the device screen before approving.
  5. Broadcast — your wallet sends the signed transaction to the network. It enters the mempool (a waiting room of unconfirmed transactions) until a miner includes it in a block.

Confirmation is the “it settled” signal. Unconfirmed means the network has heard about your transaction but it is not yet in a block. Confirmed means it was included; each later block that builds on that one adds another confirmation. Wallets show a count. For learning, wait until your wallet shows at least one confirmation before you relax; for anything that matters more, wait for the number the counterparty (or your own caution) asks for. Do not assume card-speed finality.

Why the instant-card mental model fails. Card networks often show “approved” in a second and reverse mistakes later through institutions. Bitcoin transfers that spend your keys are final once mined and deep enough in the chain; a wrong address usually means a wrong destination with no undo button. Faster payments come later with tools like Lightning (Chapter 20). On-chain first sends teach patience on purpose.

Sending to yourself. Paying a receive address from the same wallet is a classic drill: you practice the flow, see fees and confirmations, and keep control of the coins. You still pay a network fee; nothing is “free practice” on-chain.

If it sits pending. Congestion, a low fee, or a wallet still syncing can leave a send unconfirmed for a while. Do not panic-broadcast a second copy to “push” it. Check the tx id; wait; adjust fee only with wallet features you trust. Chapter 12 covers the waiting room.

Watch-outs

  • Wrong address, right amount — The dangerous mistake. Verify destination before you approve. Test amounts limit the blast radius.
  • No buy tips here — This lesson does not tell you where or whether to purchase bitcoin. It only covers moving units you already can spend.
  • “It left my wallet” ≠ confirmed — Broadcast and confirmation are different moments. Treat unconfirmed as “in flight.”
  • Support will not “speed it up” for your seed — Anyone asking for seed words, remote access, or a fee to a random address to “unstick” a transaction is a scam path (Chapter 18).
  • Fees are not a percentage of the amount — They relate to transaction size and demand for block space. Tiny sends can still pay a noticeable fee; that is normal, not a glitch.

You now can…

  • Walk through a send: destination → amount → fee → approve → broadcast → wait for confirmation.
  • Drop the instant-card expectation and treat confirmation as part of the payment.
  • Prefer tiny practice amounts so mistakes stay educational.

What next?

Ebook: continue to Ch 10

Back one stepReturn to map