What is Bitcoin—from first transaction to security budget

Why it matters

The beginner story—digital scarcity without a central issuer—is useful but incomplete. Evaluating Bitcoin requires understanding how transactions, fees, mining economics, node validation and custody interact.

UTXOs, transactions and the mempool

Bitcoin tracks spendable outputs rather than a single account balance. A transaction consumes eligible outputs and creates new ones, often including change back to the sender.

After validation, an unconfirmed transaction can be relayed among nodes and held in their local mempools. Mempools are not one global queue, so contents and fee estimates can differ.

Mining orders history

Miners assemble candidate blocks and repeatedly hash a header until work satisfies the current target. Nodes independently reject blocks that violate consensus rules, even if substantial computation produced them.

Difficulty adjusts to keep block production near the protocol target as total hash power changes. A halving reduces the block subsidy on a programmed schedule; transaction fees then matter increasingly to miner revenue.

Fees, settlement and Lightning

Block space is limited, so users compete through fees when demand rises. Confirmation is probabilistic: additional valid blocks deepen the cost of replacing the accepted history.

Lightning moves many payments through channels and settles their net result back to Bitcoin. It can improve speed and cost for suitable payments, while adding channel liquidity, routing, availability and backup considerations.

The honest tradeoffs

Bitcoin's security budget combines subsidy and fees. Its durability depends on mining economics, distributed validation, maintainable software and social willingness to preserve core rules.

Mining pools, custodians, hardware supply chains and developer coordination can concentrate influence without giving any one party unlimited control. Governance is constrained and plural—not absent.