How Bitcoin Works: What Confirms a Payment and What a Wallet Controls

A source-based walkthrough of Bitcoin addresses, private keys, the blockchain, and confirmation times, written for holders who care about access continuity and recovery readiness.

Bitcoin is often described in ways that mix the wallet you hold, the network that records payments, and the mining process that confirms them. Separating those three layers is the most useful thing a holder can do, because each layer has a different failure mode and a different backup requirement. The explanations below follow the overview published on Bitcoin.org, which notes that a new user can get started without understanding the technical details (c06).

The short version: a wallet generates an address and holds a private key, transactions are signed with that key, and the blockchain records confirmed transfers. Mining confirms pending transactions and keeps the network's chronology and neutrality intact (c17, c18). Everything else follows from those pieces.

Wallet, address, and key: who controls what

Once you install a Bitcoin wallet on a computer or mobile phone, it generates your first Bitcoin address, and you can create more whenever you need one (c07). You disclose addresses to friends so they can pay you, or so you can pay them (c08). Bitcoin.org compares this loosely to email, with one important difference: addresses should be used only once (c09). That single-use guidance is the practical reason address management matters more than it first appears.

The wallet also keeps a secret piece of data called a private key, used to sign transactions and provide a mathematical proof that they came from the wallet's owner (c14). The signature also prevents anyone from altering a transaction after it has been issued (c15). For a holder thinking about access continuity, this is the core fact: the wallet interface is convenience, while the private key is the authority. A wallet that will not open is an inconvenience; a private key that is lost or exposed is a different problem entirely.

The blockchain as a shared record

The blockchain is a shared public ledger that the entire Bitcoin network relies on (c10). All confirmed transactions are recorded in it, which lets wallets calculate their spendable balance and lets the network verify that the sender is authorized to spend those coins (c11). The integrity and chronological order of the blockchain are protected by cryptography (c12).

A transaction is a transfer of value between Bitcoin wallets that gets recorded in the blockchain (c13). All transactions are broadcast to the network and usually receive their first confirmation within about 10 to 60 minutes through mining (c16). Mining is a distributed consensus system used to confirm pending transactions by including them in the blockchain (c17). It enforces chronological order, protects network neutrality, and allows different computers to agree on the state of the system (c18).

For a reader focused on continuity, the 10 to 60 minute window is a planning number, not a guarantee. It describes typical first confirmation, not a promise about any single payment. A payment that has been broadcast but not yet confirmed is a different state from one recorded in the blockchain, and treating those two states as equivalent is where a lot of practical confusion starts.

A worked access-continuity scenario

Suppose a holder receives a payment to a freshly generated address. The wallet shows a pending transfer, then a confirmed one after the usual 10 to 60 minute window (c16). Now suppose the phone is lost. The address and the transaction still exist in the shared ledger (c10, c11), but spending from that wallet requires the private key that signs transactions (c14).

This is the distinction worth internalizing: the network does not need your device to keep the record, but you need your key material to act on it. Backup planning therefore centers on the secret data the wallet keeps (c14), not on the app's screen or the phone itself. Bitcoin.org does not describe backup procedures on this page, so the exact method is outside what this overview establishes.

What the source does not say

Several things a careful reader might expect are not established by this overview, and should not be assumed from it.

How to read the confirmation process without overclaiming

The overview frames mining as the mechanism that turns a broadcast transaction into a recorded one (c16, c17). That framing is useful for setting expectations: a transaction moves from pending to recorded, and only recorded transactions appear in the ledger wallets use to calculate balances (c11). The chronological ordering and neutrality described for mining (c18) explain why the network can agree on a single state rather than diverging copies.

What the page does not do is quantify risk. It gives no probability that a payment confirms within any specific minute, no rule for how many confirmations are enough for a given amount, and no description of reorg behavior. A reader who needs those thresholds is beyond this source and should treat any specific number as unverified.

What a holder can reasonably take away

Three statements carry most of the practical weight. Addresses are generated by the wallet and should be used once (c07, c09). The private key signs transactions and prevents later alteration (c14, c15). The blockchain records confirmed transfers and lets wallets compute balances and verify authorization (c10, c11).

Everything about access continuity follows from keeping the key material under your control while the public record does its job independently of your device. The overview's own framing is that beginners do not need the technical details to start (c06), which is fair, but anyone holding meaningful balances eventually needs to know which piece is the record and which piece is the authority.

Sources

Informational only. Not financial, legal or investment advice. Check the primary sources listed above before you act on anything here.