Bitcoin basics: the white paper and key facts
Bitcoin was first described in a nine-page paper by Satoshi Nakamoto, published on 31 October 2008. Here is what each section says in plain English, followed by the key facts a company should know, each with a source.
The white paper, section by section
The paper has twelve numbered sections. Section 1 sets out the problem, sections 2 to 6 describe how the system works, and sections 7 to 12 cover storage, light clients, privacy and security.
- Introduction. Online payments rely on banks and payment firms acting as trusted middlemen. Because their payments can be reversed, someone has to settle disputes, which adds cost, makes very small payments impractical and pushes merchants to ask customers for more information. The paper proposes payments based on cryptographic proof instead of trust, so two parties can transact directly.
- Transactions. A coin is described as a chain of digital signatures. Each owner passes it on by signing a record that points to the previous transaction and to the next owner's public key. Signatures alone cannot stop the same coin being spent twice, so every transaction has to be announced publicly and everyone has to agree on one history of the order in which they happened.
- Timestamp server. Transactions are grouped into blocks. Each block is hashed together with the hash of the block before it, so the blocks form a chain. Every new block reinforces the ones before it, which proves the earlier data existed at that time.
- Proof of work. To add a block, a participant must find a number that makes the block's hash meet a target, which takes a great deal of computing work but is quick for anyone to check. Changing an old block would mean redoing its work and the work of every block after it. The chain with the most accumulated work counts as the agreed history, and the difficulty adjusts so blocks keep arriving at a steady average rate.
- Network. The paper lists the steps: transactions are broadcast to all nodes, nodes gather them into a block and work on its proof, a node that finds one broadcasts the block, and other nodes accept it only if every transaction in it is valid and not already spent. Nodes show acceptance by building the next block on top of it.
- Incentive. The first transaction in each block creates new coins for whoever produced the block. This is how new coins are issued without a central issuer. Transaction fees are a second incentive, and once the planned number of coins has been issued, fees can replace new coins entirely. The paper argues that an attacker with a lot of computing power would earn more by following the rules than by undermining them.
- Reclaiming disk space. Old transactions can be pruned once they are buried under enough blocks, because each block stores a single summary hash (a Merkle root) of its transactions. A block header without its transactions is about 80 bytes, so keeping every header needs only a few megabytes a year.
- Simplified payment verification. A user can check that a payment is included in the chain without running a full node, by keeping only the block headers and asking for proof that the transaction sits in a block. This is reliable while honest nodes control the network. The paper notes that "businesses that receive frequent payments will probably still want to run their own nodes for more independent security and quicker verification".
- Combining and splitting value. A transaction can have several inputs and outputs, so value can be combined and split. Usually there is one output for the payment and one returning change to the sender.
- Privacy. Banks keep transactions private by limiting who can see them. Bitcoin instead makes every transaction public and keeps privacy by not tying public keys to identities. The paper suggests a new key pair for each transaction, and warns that some linking is unavoidable when several inputs are spent together.
- Calculations. The paper works out the chance that an attacker could build a longer alternative chain and rewrite recent history. That chance falls very quickly with each extra block the attacker is behind, which is why recipients wait for several confirmations before treating a large payment as settled.
- Conclusion. The paper sums up a system for electronic payments that does not rely on trust. Nodes need little coordination, can leave and rejoin at will, and agree on history by accepting the chain with the most proof of work. Any rules and incentives needed can be enforced through this same mechanism.
Key facts
Each fact links to its source: the Bitcoin Core software, Bitcoin's developer documentation or the public block chain. Live figures come from mempool.space.
| Supply limit | The software caps the amount of bitcoin at 21 million. Because the subsidy halves and is rounded down to whole satoshis, total issuance will end just under that figure.Source: Bitcoin Core, Bitcoin Core |
|---|---|
| Issuance and halvings | New bitcoin is paid to whoever produces each block, as the block subsidy. It started at 50 BTC and halves every 210,000 blocks, roughly every four years. The fourth halving was at block 840,000 on 20 April 2024, and the subsidy has been 3.125 BTC since then. Live: block loading, subsidy loading, next halving at block loading, loading blocks from now.Source: Bitcoin Core, Bitcoin Core, mempool.space |
| Block time and difficulty | The network targets one block every 10 minutes on average. Every 2,016 blocks, about two weeks, the difficulty resets up or down so the average stays close to that target.Source: Bitcoin Core, Bitcoin developer documentation |
| Satoshis | One bitcoin is 100,000,000 satoshis, the smallest unit recorded on the chain. Fees are usually quoted in satoshis per virtual byte.Source: Bitcoin Core, Bitcoin developer documentation |
| Genesis block | The first block was created on 3 January 2009. Its first transaction includes the text of that day's Times headline: "Chancellor on brink of second bailout for banks".Source: Bitcoin Core, mempool.space |
| Proof of work | Block producers (miners) repeatedly hash a block header with SHA-256 until the result is below a target. Rewriting history would mean redoing that work for every later block.Source: Satoshi Nakamoto, Bitcoin developer documentation |
| Keys | Bitcoin is controlled by private keys. Whoever can sign with the right keys can move the coins. There is no bank to reverse a payment, and if every key needed to spend is lost, no one can recover the funds.Source: Bitcoin developer documentation |
| Why custody matters for a company | Because control follows the keys, key management is a company's main operational control. A multisig set-up means no single person can move funds alone and one lost key does not lose access. Read the custody models, how self-managed multisig works, and why we do not recommend single-signature wallets for a company.Source: Bitcoin BIPs |
| Three ways to hold exposure | A company can hold bitcoin itself, ideally in a multisig it controls (alone or with a specialist key holder); use a regulated custodian that holds it on the company's behalf; or buy an exchange-traded product through a brokerage account, such as a spot bitcoin ETF in the US or a crypto ETN in the UK. With an exchange-traded product the company owns a security, not bitcoin. See the main models.Source: SEC, FCA |
Loading live block data.
Where to go next
- Market and network context: live price, block height, hash rate and fees, data only.
- Custody options: multisig, a regulated custodian or an exchange-traded product.
- Sizing an allocation and treasury policy.
Sources
Primary sources only. Each link was checked on 29 October 2026. Rules change, so confirm the current version with your adviser.
- Satoshi NakamotoBitcoin: A Peer-to-Peer Electronic Cash System (white paper, 31 October 2008, PDF)
- Bitcoin Coresrc/consensus/amount.h: COIN (100,000,000 satoshis) and MAX_MONEY (21 million BTC)
- Bitcoin Coresrc/kernel/chainparams.cpp: halving interval of 210,000 blocks, 10 minute block target, two week retarget, genesis block
- Bitcoin Coresrc/validation.cpp: GetBlockSubsidy, 50 BTC halved every 210,000 blocks
- Bitcoin developer documentationBlock chain guide: proof of work, difficulty every 2,016 blocks, block subsidy
- Bitcoin developer documentationTransactions guide: public keys, private keys and signatures
- Bitcoin developer documentationGlossary: one bitcoin equals 100,000,000 satoshis
- mempool.spaceBlock 0, the genesis block (3 January 2009)
- mempool.spaceBlock 840,000, the fourth halving (20 April 2024)
- Bitcoin BIPsBIP 11: M of N standard transactions (multisig)
- SECInvestor Bulletin: exchange-traded products providing exposure to bitcoin and ether (September 2024)
- FCAFCA opens retail access to crypto ETNs (in force 8 October 2025)
One email. The whole library.
Policy checklist, board paper, recovery drill record, document pack and the rest, in one send. Then one short Thursday lesson for small companies in the UK and the US.
Free. One email with the whole template library, then one short lesson each Thursday. Unsubscribe at any time. See our privacy notice.
This is general information and education only. It is not financial, investment, tax, accounting, legal or regulatory advice, and it is not a recommendation to buy, sell or hold bitcoin or any other asset. It does not take account of your circumstances or those of your company. You must obtain your own official professional advice to confirm this information is correct before acting on it.
Rules change. This information is correct to our understanding at the last-reviewed date, but it may be incomplete or out of date, and official sources take precedence. Bitcoin is volatile. A company that buys it could lose some or all of the money it puts in.
Using this site does not create an adviser or client relationship. IoT Financial is not authorised or regulated by the Financial Conduct Authority (FCA) and is not registered with the US Securities and Exchange Commission (SEC) as an investment adviser. Read the full disclaimer.