The short answer
A Bitcoin wallet signs a transaction spending available outputs. Network nodes verify the signature and rules; miners compete to include valid transactions in a proof-of-work block. Full nodes then verify that block for themselves. This combination provides a shared transaction history without placing one operator in charge.
Start with the unspent-transaction-output model
Instead of one centralized account number with an editable balance, Bitcoin records unspent transaction outputs, often called UTXOs. A transaction consumes specific outputs and creates new ones. A wallet calculates the spendable value of outputs it can authorize. It may produce a change output back to the sender when the selected input amount exceeds the payment and fee.
Think of paying $6 with a $10 banknote: you receive $4 in change. Bitcoin's units are digital and outputs can be split differently, but the analogy helps explain why one outgoing payment may produce both a recipient output and a change output.
- Inputs identify outputs being spent.
- Outputs define new spending conditions.
- The difference between input and output value is the transaction fee.
Keys authorize; nodes decide validity
A private key signs a transaction; the corresponding public-key conditions let nodes check authorization. The key itself never has to be broadcast. A signature is necessary for most everyday spends, but it is not enough if the transaction violates other consensus rules.
A fully validating node checks transaction and block rules, including whether referenced outputs are still unspent and whether the block is valid. An explorer website or custodial app may show a convenient view, but its screen is not the consensus authority.
- Private keys authorize spending, not ownership identity.
- Full nodes enforce the rules independently.
- An address is a receiving representation, not your complete wallet.
Mining, difficulty and the shared history
Miners assemble candidate blocks and repeatedly vary block data to find a hash below the network's current target. This is proof of work. Finding a valid hash is costly and uncertain; verifying it is comparatively cheap. Miners earn a block subsidy and fees only when their valid blocks become part of the accepted chain.
Bitcoin targets an average interval of approximately ten minutes by adjusting difficulty every 2016 blocks. Actual blocks arrive unpredictably. A powerful miner can propose blocks, but cannot make honest full nodes accept invalid inflation or a transaction that breaks consensus rules.
- Hashing is not solving a meaningful scientific puzzle.
- Difficulty adjusts to the observed rate of block production.
- A valid miner proposal is still checked by nodes.
Why confirmation counts matter
Before confirmation, a transaction may sit in nodes' mempools and can be replaced or excluded depending on circumstances and policy. Once a block includes it, it has one confirmation. Each later accepted block increases the work that would generally be needed to reorganize the history.
A small everyday payment and a property-sized transfer should not be treated as having identical risk. Wallets and merchants choose their own confirmation policies. Lightning uses a different, channel-based approach to make fast small payments possible.
- Unconfirmed does not mean guaranteed.
- More confirmations change risk, not the transaction's amount.
- Network congestion can affect waiting time.
Try tracing one fictional payment
Suppose your wallet controls a 0.005 BTC output. You send 0.002 BTC to a friend. The wallet can create one recipient output plus change to a new address you control, minus a fee determined by the serialized transaction's weight and current fee rate.
Ask which component would prevent you from spending the same original output again. The answer is not a gatekeeper at the wallet company. It is the set of rules checked by validating nodes, together with proof-of-work consensus about which valid history to follow.
- Look for input, recipient output, change, and fee.
- Find the difference between mempool acceptance and block confirmation.
- Read the white paper alongside the current protocol guide.
At each stage, who does what?
Use this original comparison to turn the explanation into a practical choice. These scenarios illustrate different constraints; the right answer depends on circumstances and current provider rules.
| Situation | What matters |
|---|---|
| Wallet constructs payment | Selects inputs and outputs and signs with the necessary keys. |
| Miners propose a block | Compete to produce work and collect eligible transaction fees. |
| Full nodes validate | Check the block and transactions independently against consensus rules. |
Frequently asked questions
Is Bitcoin a blockchain?
Bitcoin uses a proof-of-work blockchain as its shared transaction history, but the network also depends on validation rules, nodes, wallets and economic incentives.
What happens if miners disagree?
Valid competing tips can temporarily exist. Nodes converge on the valid chain with the most cumulative proof of work under their consensus rules.
Can a miner simply create extra bitcoin?
Not under the existing rules followed by validating nodes; an invalid block subsidy would be rejected.
Sources and further verification
These sources support the protocol, operational, or regulatory foundations described above. Provider policies and laws can change; check their current versions before acting.
Editorial education, not personalized investment, legal, security, or tax advice. No purchase of Bitcoin is required to learn about it.