Bitcoin as a protocol, network and monetary unit
When people say Bitcoin, they often combine at least three ideas. The Bitcoin protocol defines transaction, block and consensus rules. The network is made of nodes, miners, peers and messages. BTC is the accounting unit, divisible down to satoshis and transferred through transactions.
Unlike a bank account, the protocol has no central server that simply rewrites a balance. Nodes independently check whether the rules allow specific transaction outputs to be spent. Miners group valid transactions into blocks, but they cannot create coins outside the rules.
- the protocol defines rules
- the network transmits and validates data
- BTC and satoshis are accounting units
- a node can validate rules without trusting an exchange
Keys, addresses and wallets: where BTC really is
Coins do not sit inside a mobile app or hardware wallet. The blockchain records which UTXOs can be spent under a condition. A private key creates a digital signature, while a wallet stores keys and helps build a new transaction.
An address is a convenient encoding of a receiving condition, not the private key itself. A seed phrase can restore many keys through deterministic-wallet standards, so losing or copying it means losing or transferring control. An exchange may show an internal balance until a user withdraws BTC to an address they control.
- never share a seed phrase
- verify an address on the device screen
- a receiving address is not a private key
- custodial exchange and self-custody have different risks
Transactions and the UTXO model
Bitcoin does not keep one simple balance for every address. A transaction spends previous unspent outputs, called UTXOs, and creates new ones. An input points to a previous output and includes proof of spending authority; an output sets an amount and a condition for the next owner.
If an input is larger than the payment, the difference normally returns to a change address. A fee is not a separate output: it is inputs minus outputs. That is why transaction byte size and the number of inputs and outputs matter to the fee.
- inputs spend old UTXOs
- outputs create new UTXOs
- change returns the remainder to the wallet
- fee equals inputs minus outputs
How a transaction travels through the network
A wallet signs a transaction and sends it to peers. A node checks format, signatures, double-spend conflicts and other rules before relaying it. A valid but unconfirmed transaction usually enters the node's local mempool.
Miners choose transactions from their available set, often using fee rate in satoshis per virtual byte. Once a transaction enters an accepted block, it has one confirmation. Further blocks raise the cost of rewriting history, although Nakamoto consensus has no instant absolute finality.
- nodes validate before relay
- mempool is a queue of unconfirmed transactions
- miners optimize a block for reward and fees
- confirmations are chain depth
Mining and the block reward
A miner builds a candidate block, adds a coinbase transaction and searches for a header whose double-SHA-256 is below target. A valid block is broadcast. Full nodes check Proof of Work, the previous hash, Merkle root, transactions, limits and reward.
The reward consists of block subsidy and transaction fees. Subsidy changes through the halving schedule, while fees depend on demand for block space. Hashrate gives a miner a statistical share of work, not a guaranteed payment. A pool usually pays more frequently than solo mining, with its own fee and payout rules.
- a miner cannot change reward rules alone
- subsidy decreases through halvings
- fees depend on block-space demand
- a pool reduces payout variance but not market risk
Why BTC supply is limited
The supply limit is the result of coinbase and halving rules, not a company promise. Every full node checks that new coins do not exceed the permitted reward. If a miner creates extra BTC, honest nodes reject the block even if it has enough hashrate.
It is useful to separate protocol issuance from liquid supply. Keys can be lost, coins can remain dormant and demand changes daily. A maximum-supply figure is therefore not a price forecast.
- nodes enforce issuance rules
- halving reduces subsidy
- lost keys affect accessible liquidity
- scarcity does not guarantee a market price
Nodes, miners and exchanges have different jobs
A full node stores and validates the chain under the rules. A miner buys power and hardware, builds candidate blocks and spends computation on Proof of Work. An exchange matches orders and may custody assets. None of these is a central Bitcoin server.
An exchange price matters to a miner, but an exchange outage does not rewrite UTXOs. Separate market data, blockchain data and calculator assumptions when reading the ecosystem.
- nodes validate
- miners package transactions and search Proof of Work
- exchanges match orders and custody assets
- BTC price and chain state are different data sources
Security: double-spends, reorgs and 51%
A double-spend attempts to use one UTXO in conflicting transactions. Nodes cannot treat both as final, and the network selects the chain with the greatest accumulated Proof of Work. Short forks and reorgs can occur when competing blocks are found close together.
A 51% attack does not magically create BTC. It can increase an attacker's ability to censor or reorganize their own spending, but it does not provide other people's private keys or bypass signature and node validation rules. Security combines protocol, hashrate distribution, economics and key-management practice.
- a signature cannot spend someone else's UTXO
- a reorg can change a recent transaction's status
- more confirmations raise attack cost
- 51% does not cancel full-node rules
How to read Bitcoin without self-deception
For technical verification, inspect txid, inputs, outputs, fee rate, block height, confirmations and inclusion time. For the network, inspect difficulty, hashrate, mempool, fees and pool distribution. For mining economics, inspect actual power, J/TH, tariff, uptime, pool fee and equipment cost.
Do not confuse network hashrate with one ASIC's income, or a market chart with a pool's solvency. Bitcoin becomes clear as a system: [SHA-256 in Bitcoin](sha-256-u-bitcoin) explains hashing, while the [Bitcoin blockchain](bitcoin-blokcheyn-uto) explains records and confirmations.
- separate protocol data from exchange price
- verify a txid in an independent explorer
- read fee rate in sat/vB
- model mining with scenarios rather than one attractive number
Bitcoin transaction life cycle
A payment passes through independent stages before becoming part of chain history.
Three layers not to confuse
One ecosystem has different sources of truth for different questions.
A simple miner-reward model
Profitability starts with expected work share, not a model name.
| Component | What it stores or does | Who validates it |
|---|---|---|
| Private key | Secret used to create a signature | Wallet and cryptographic rules |
| Address | Encoded receiving condition | Node during output validation |
| UTXO | Unspent transaction output | Full node |
| Mempool | Node's unconfirmed transaction set | Each node locally |
| Block | Header and transactions | Network full nodes |
| Confirmation | Transaction depth after its block | Explorer and node |
| Exchange balance | Exchange database record | Exchange, not Bitcoin protocol |
Real photos and source material
These photographs and diagrams are sourced from public archives. Open the source link to check the author and license.
.jpg)
Want to check the numbers for your ASIC right away?
Open calculator →
