Addresses & Receiving

Hook

When someone pays you in bitcoin, they do not send a file to your phone. They lock value to a destination your wallet can unlock—an address (or a payment invoice that includes one). Sharing that destination correctly is the whole skill of receiving.

One idea

A Bitcoin address is a payment destination derived from your keys—not a password, not a bank account, and not the coins themselves—and using a fresh address for each receive is normal because reusing the same one makes your activity easier to link.

Plain walkthrough

What you share. To receive, open your wallet’s receive screen. It shows an address (a string of letters and numbers) and often a QR code of the same thing. Some wallets also create an invoice—an address plus an amount and optional label—so the payer sees what you asked for. Either way, you are handing them a destination, not unlocking your wallet.

Address ≠ password ≠ account. An address does not log anyone into your funds. Knowing where you can be paid is not the same as being able to spend. Spending still requires your private keys (backed up by your seed phrase from Chapter 7). Think of the address as a mailbox slot on a public street: anyone can drop something in; only the person with the key to that box can take mail out. The metaphor stops there—the “box” is cryptographic control on the shared ledger, not a physical container.

Where the coins actually go. When a payment confirms, the network records that those units are locked to conditions your wallet’s keys can satisfy. Your balance updates because your wallet recognizes outputs it can spend—not because a file arrived in the app.

Fresh addresses are normal. Modern wallets can generate many receiving addresses from one seed. Prefer a new address (or a new invoice) for each payment when the wallet offers that. Reusing one address forever is still valid on the network, but it ties payments together for anyone watching the public ledger—friends, merchants, chain analysts, or curious strangers. Privacy here is about unlinkability, not secrecy of the ledger itself (Bitcoin’s history is public).

What “reuse hurts privacy” means in practice. If Alice always pays the same address, observers can guess that those payments belong together. If Bob uses a fresh address each time, linking them is harder without other clues. Fresh addresses do not make you invisible; they are a basic hygiene habit your wallet already supports.

Checking you received. After someone pays, your wallet may show the payment as unconfirmed until it is included in a block (Chapter 9 and 13). Wait for your wallet’s confirmation count before treating the money as settled for anything important. You can also look up the transaction on a block explorer (a website that displays ledger data) using the tx id your wallet shows—optional, not required on day one.

Invoices vs raw addresses. A raw address is enough for many transfers. An invoice packages destination + amount so the payer’s wallet can pre-fill the send screen. Both are fine; just confirm the address (or QR) came from your wallet’s receive screen, not from a chat that “updated” it for you.

Watch-outs

• Address poisoning / look-alikes — Scammers sometimes send tiny amounts from addresses that resemble ones you used, hoping you copy the wrong string next time. Always copy the receive address from your wallet (or scan its QR), not from an old text thread.
• “Send here to verify” — Nobody needs you to receive (or send) to prove an address is yours for support. Fake support uses urgency; real wallets never need your seed or a surprise deposit to “activate.”
• QR from strangers — A QR is just data. Scan only codes you generated, or codes from people you already trust for that payment.
• Reuse is not “broken” — Reused addresses still receive fine. The cost is privacy and linkability, not network rejection.
• Address is not the vault — Losing a screenshot of an old address does not lose coins. Losing the seed that can spend those coins does.

You now can…

• Share a receive address or invoice from your own wallet without treating it like a password.
• Prefer fresh addresses and explain why reuse weakens privacy on a public ledger.
• Separate destination (address) from control (keys / seed).