What Is Bitcoin?
Bitcoin is digital money that works without a bank. There is no company behind it, no CEO, no central server. Instead, thousands of computers around the world (called nodes) independently enforce the same rules, and anyone can verify that those rules are being followed.
It was created in 2008 by the pseudonymous Satoshi Nakamoto, who published a 9-page whitepaper titled "Bitcoin: A Peer-to-Peer Electronic Cash System." The first block (the "genesis block") was mined on January 3, 2009.
At its core, Bitcoin answers a question that had stumped computer scientists for decades:
How can two strangers on the internet transfer value directly, without trusting each other, and without trusting any middleman?
The Problem It Solves: Double Spending
Physical cash works because you can't be in two places at once. If you hand someone a $20 bill, you don't have it anymore. But digital files can be copied infinitely. If "money" is just a file, what stops you from sending the same file to two different people?
This is the double-spend problem. Before Bitcoin, every digital payment system solved it the same way: a trusted central authority (a bank, PayPal, Visa) keeps a master ledger and decides which transactions are valid. You trust them not to cheat, censor, or fail.
Bitcoin's breakthrough is replacing that central authority with a decentralized network and a proof-of-work consensus mechanism. No single entity controls the ledger. Instead:
- Every node keeps a full copy of every transaction ever made (the blockchain).
- New transactions are broadcast to all nodes, who independently verify them.
- Miners compete to bundle transactions into blocks by solving a computational puzzle.
- The puzzle's difficulty adjusts so that globally, a new block is found roughly every 10 minutes.
- Once a transaction is buried under several blocks, reversing it would require redoing an enormous amount of computation, making fraud impractical.
Key Ideas You Need
Before we dive into code, here are the fundamental concepts that everything else builds on:
UTXOs, Not Balances
Bitcoin doesn't track "account balances." Instead, it tracks unspent transaction outputs (UTXOs). Think of them as individual coins of varying denominations. To pay someone, you consume one or more coins and create new ones.
Keys & Signatures
You don't "own" bitcoin by having a file. You own it by having a private key that can produce a digital signature proving you're authorized to spend a specific UTXO. Lose the key, lose the bitcoin.
Script
Every UTXO has a tiny program (a "script") attached to it that defines the spending conditions. Usually: "provide a valid signature for this public key." But scripts can encode timelocks, multisig, and other conditions.
Blockchain
Blocks are chained together by including the hash of the previous block in each new block's header. Changing any old block would change its hash, breaking the chain and making tampering evident and impractical.
Mining & Proof of Work
Miners repeatedly hash a block header with different nonces until the hash is below a target value. This costs real energy. The first miner to find a valid hash earns the block reward (currently 3.125 BTC) plus transaction fees.
Peer-to-Peer Network
There's no central server. Nodes discover each other and gossip transactions and blocks over TCP connections. Anyone can run a node. The network has ~15,000 reachable nodes worldwide.
How a Bitcoin Payment Actually Works
Let's say Alice wants to pay Bob 0.05 BTC. Here's what happens, step by step, in plain English. (Every one of these steps is explored in depth in later chapters.)
The Big Picture
Here it is all at once:
Notice what's not in this picture: no bank, no payment processor, no account, no identity verification. Alice proved ownership with math (a digital signature). The network proved the transaction's validity through independent verification. A miner proved the block's legitimacy with real computational work. And Bob can verify all of it himself by running a node.
What Is Bitcoin Core?
Bitcoin Core is the reference implementation of the Bitcoin protocol, the original software started by Satoshi Nakamoto, now maintained by hundreds of open-source contributors. When we say "Bitcoin's rules," we mean the rules enforced by this code.
It's a single C++ program (bitcoind) that does everything:
- Full node: downloads and validates every block since 2009
- Transaction pool: holds unconfirmed transactions waiting to be mined
- P2P relay: connects to other nodes, shares blocks and transactions
- Wallet (optional): manages keys, creates and signs transactions
- RPC interface: external tools and apps can query and control the node
The codebase is ~300,000 lines of C++, with extensive test coverage. It's one of the most carefully reviewed open-source projects in existence, because bugs here can mean lost money.
How to Read This Guide
This guide is structured as a book with 14 chapters, designed to be read in order:
Each chapter builds on the ones before it. By Chapter 10, you'll see the entire system come alive as a single transaction travels from wallet to blockchain. Chapters 11–14 cover advanced and evolving topics for readers who want the complete picture.
Want the end-to-end picture first? Skip ahead to Chapter 10: The Complete Transaction Lifecycle for a detailed technical walkthrough. You can then come back here and work through the chapters in order, and everything in Chapter 10 will click on a deeper level.