How Bitcoin Works

This guide covers how Bitcoin actually works at a structural level, from the way individual transactions are constructed to the consensus mechanism that holds the entire network together. You will find sections on the UTXO model, blocks and the blockchain, mining and proof of work, consensus rules, nodes and network architecture, and the misconceptions that trip up even experienced users. I have been running nodes, verifying transactions, and working with Bitcoin daily for over a decade, and the explanations here come from that hands-on practice. If you are completely new, you may want to read the Start Here orientation first, then come back to this page for the deeper technical foundation.

Transactions and the UTXO Model

Every Bitcoin transaction is, at its core, a signed message that says: take these specific coins and send them to these new addresses. That sounds simple, but the way Bitcoin tracks ownership is different from what most people expect.

Bitcoin does not use an account-balance model the way a bank does. There is no database entry somewhere that says "this address holds 3.5 bitcoin." Instead, the network tracks unspent transaction outputs, or UTXOs. Think of each UTXO as a specific coin with a specific value. When you receive 0.25 bitcoin in a transaction, that creates a UTXO locked to your address. When you want to spend it, you reference that specific UTXO as an input to your new transaction, prove you own it with your private key, and the network consumes it entirely.

This is where change comes in. If your UTXO is worth 0.25 bitcoin and you only need to send 0.1, the transaction creates two new outputs: 0.1 to the recipient and roughly 0.15 back to an address you control. The difference between the total inputs and total outputs is the transaction fee, which goes to the miner who includes your transaction in a block.

The UTXO model matters for privacy and efficiency. Each unspent output is independent. You can consolidate small UTXOs when fees are low, or deliberately keep them separate for privacy. Wallet software handles this automatically for most people, but understanding the underlying model helps you make smarter decisions about fee management, coin selection, and the security practices that protect your funds.

Blocks and the Blockchain

Transactions do not confirm individually. They are collected into blocks, and each block is cryptographically linked to the one before it. That chain of blocks, going all the way back to January 3, 2009, is what people mean when they say "the blockchain."

A block is essentially a container. It holds a set of valid transactions, a reference to the previous block's hash, a timestamp, and a piece of data called a nonce that miners adjust during the mining process. The block header is what gets hashed, and that hash must meet a specific difficulty target for the block to be accepted by the network.

Each block can hold a limited amount of data. The current practical limit, after the SegWit upgrade, is about 4 megabytes of weight units, though most blocks average around 1.5 to 2.5 megabytes. This constraint is intentional. It keeps the cost of running a full node manageable, which is critical for decentralization. A new block is found approximately every ten minutes on average, though the actual interval varies from seconds to over an hour depending on probabilistic mining outcomes.

The chain structure is what makes the ledger tamper-resistant. If someone tried to alter a transaction in block 500,000, the hash of that block would change. That would break the link to block 500,001, which would break the link to 500,002, and so on through every subsequent block. Rewriting history would require redoing the proof of work for every affected block faster than the rest of the network produces new ones. With today's hashrate, that is computationally infeasible.

Mining and Proof of Work

Mining is the process that secures the network and determines which transactions get confirmed. Miners compete to find a valid block hash by repeatedly hashing the block header with different nonce values until the result falls below the current difficulty target. This is raw computational work. There are no shortcuts.

The difficulty adjusts every 2,016 blocks, roughly every two weeks. If blocks have been arriving faster than the ten-minute target, the difficulty increases. If they have been arriving slower, it decreases. This self-regulating mechanism is one of the most elegant pieces of the protocol. It means the issuance schedule stays predictable regardless of how much or how little mining power joins the network.

Miners are compensated in two ways: the block subsidy and transaction fees. The subsidy started at 50 bitcoin per block in 2009 and halves approximately every four years. As of the most recent halving, the subsidy is 3.125 bitcoin per block. Over time, transaction fees will become a larger proportion of miner revenue as the subsidy continues to decline toward zero.

A common analogy: mining is like a global lottery that runs every ten minutes. The more computational power you contribute, the more lottery tickets you hold. But the winning ticket is always verifiable by anyone in a fraction of a second. That asymmetry between the cost of producing and the ease of verifying is the core insight of proof of work.

Consensus Rules

Consensus rules are the set of conditions that every node on the network independently enforces. If a block or transaction violates any of these rules, every properly configured node will reject it automatically. No voting. No committee. No appeals process.

The most important consensus rules include: the 21 million supply cap, the block size limit, the requirement that each transaction input must reference a valid unspent output, the rule that a coinbase transaction cannot be spent until 100 blocks have passed, the difficulty adjustment formula, and the scripting rules that govern how outputs can be spent. These are not guidelines. They are hard boundaries.

This is what gives Bitcoin its resistance to political influence. Even if every mining pool and every exchange agreed to change the supply cap, the tens of thousands of independent nodes running the original rules would simply reject those blocks. The network would fork, and the nodes enforcing the original rules would continue operating the Bitcoin network as it was designed. The concept of distributed consensus is well documented on Wikipedia's Bitcoin article, and the practical effect is a system that relies on cryptographic proof rather than trust.

Understanding consensus rules is the key to understanding why Bitcoin cannot be quietly changed by insiders. The rules are public. The enforcement is distributed. And any change that is not backward-compatible requires near-universal voluntary adoption by the people running the software.

Nodes and Network Architecture

A node is any computer running Bitcoin software that validates transactions and blocks according to the consensus rules. Full nodes download and verify every block since genesis. They do not trust any other participant. They check everything themselves.

This is what makes Bitcoin genuinely decentralized. The network topology is a mesh of thousands of nodes across dozens of countries, connected peer-to-peer. There is no central server. There is no master database. When your node receives a new block from a peer, it independently verifies every transaction inside it before forwarding it to its own peers. If the block is invalid, it gets discarded silently.

Running your own node is the only way to verify your own transactions without trusting a third party. When you use a mobile wallet that connects to someone else's node, you are trusting that node to give you accurate information. For small amounts, that is a reasonable trade-off. For serious holdings, it is worth running your own. The hardware requirements are modest: a basic computer with a few hundred gigabytes of storage and a reliable internet connection is sufficient.

Nodes also relay unconfirmed transactions through the mempool, the waiting area where valid transactions sit until a miner includes them in a block. The mempool is not a single entity. Every node maintains its own version, and they may differ slightly depending on when each node received each transaction. This is normal and does not affect the integrity of the confirmed chain.

If you are ready to take the practical step of holding your own keys, the Self-Custody First Steps guide walks through the process. Running a node pairs naturally with self-custody, and the Tools section has instruments to help you assess your overall sovereignty posture.

Common Misconceptions

Even people who have spent time around Bitcoin carry misconceptions that stem from bad analogies, outdated information, or surface-level media coverage. Here are the ones I encounter most frequently.

"Bitcoin is anonymous." It is not. Bitcoin is pseudonymous. Every transaction is recorded on a public ledger. If your identity is linked to an address through an exchange, a purchase, or careless handling, your entire transaction history from that address is visible. Privacy on Bitcoin requires deliberate effort and specific techniques.

"Miners control Bitcoin." Miners produce blocks, but they do not set the rules. Nodes enforce the consensus rules independently. A miner who produces an invalid block gets ignored by the network. Hashrate is economic power, but it is not governing power.

"The blockchain can be hacked." The blockchain itself has never been successfully attacked. Security incidents in Bitcoin's history have involved exchanges, wallets, or individual users, not the core protocol. The distinction matters. A bank vault can be secure even if someone leaves the front door of the building unlocked.

"Bitcoin wastes energy." Energy consumption is real, but "waste" implies no value is produced. Proof of work converts electricity into the most secure settlement network in human history. Whether that trade-off is worthwhile is a legitimate discussion. Dismissing it as waste ignores the security model entirely.

"You can send a fraction of a bitcoin, so the supply cap does not matter." Divisibility and supply are independent properties. You can divide a dollar into cents without printing more dollars. A bitcoin is divisible to eight decimal places, and the smallest unit, a satoshi, is the base unit for transactions. The supply cap of 21 million remains fixed regardless of divisibility.