An address is a shareable identifier derived from a public key; it is safe to publish and does not by itself reveal your private key or let anyone spend from it. Most modern wallets generate a fresh address for every request rather than reusing one, which improves privacy by making it harder to link multiple payments to the same person.
A received payment appears in the mempool immediately after broadcast, but is only considered settled once included in a block (one confirmation), with each additional block adding more certainty against reversal. Many exchanges and merchants wait for multiple confirmations before treating a large payment as final.
Address types matter for compatibility, not security: older wallets may not generate the newest address formats (see the 'Reading an address' lesson). If a sender's wallet cannot produce the format you gave them, ask for an alternative format rather than assuming the payment failed.
Explain more simply
To receive bitcoin, your wallet gives you an address, a string of letters and numbers, that you share with the sender, the same way you'd share a bank account number.
After the sender broadcasts the payment, it takes some time to be confirmed by the network. Your wallet will usually show it as 'pending' or 'unconfirmed' first.
Real-world analogy
Sharing an address is like handing out a mailbox slot number: anyone can drop something in, but only the person with the matching key can take it out.
Key facts
- Sharing a receiving address cannot let anyone spend your funds.
- Most wallets generate a new address per payment for better privacy.
- A payment is only final after enough confirmations; there is no built-in refund mechanism.
Common misconception
“Giving someone your bitcoin address is risky, like giving out a password.”
An address only allows people to send you money, never to take it. It is closer to a bank account number than a password; the private key, which you never share, is what protects your funds.[3]
Go deeper
Behind each address sits a script describing the spending condition. Wallets track the blockchain for outputs matching addresses they control and mark those unspent transaction outputs (UTXOs) as spendable balance, there is no single 'account balance' stored anywhere on-chain, only a sum the wallet computes.
Because payments are irreversible once sufficiently confirmed, receivers who need refund capability build that into their own process (e.g. sending back a new transaction) rather than relying on the protocol, which has no chargeback mechanism.
Quick check
Answer every question correctly (100%) to complete this lesson.
1.Can someone spend your bitcoin if they only have your receiving address?
2.When is a received payment generally considered final?
Counts towards your streak in this browser.
Extra exam questions
Every question here counts towards your accuracy, XP and rank. No guessing: every answer is explained.
Quick check
Answer every question correctly (100%) to complete this lesson.
1.Is it safe to share a Bitcoin receive address publicly?
2.Why do wallets generate a new address for each incoming payment?
3.Does reusing the same address to receive multiple payments break Bitcoin?
4.What confirms that a received payment has settled with high certainty?
5.What is a QR code commonly used for when receiving bitcoin?
6.If someone sends you bitcoin to the wrong address by mistake, what usually happens?
7.What does an unconfirmed incoming transaction sitting in the mempool mean?
8.Can a Lightning invoice be used to receive bitcoin?
Counts towards your streak in this browser.
Sources
- Bitcoin developer documentation, bitcoin.org / Bitcoin Optech glossary
- mempool.space REST API, mempool.space (open source)
Live block, mempool, fee, mining and Lightning figures shown on this site come from this API.