What it is and the problem it solves
Blockchain is a public, distributed ledger secured by cryptographic hashing and proof-of-work. It solves the double-spending problem for digital currency without a trusted authority.
The design had precursors. David Chaum proposed a blockchain-like protocol in his 1982 dissertation. In 1991 Stuart Haber and W. Scott Stornetta described a cryptographically secured chain of blocks, meant to make document timestamps tamper-proof, and in 1992 they and Dave Bayer added Merkle trees. Nakamoto published the bitcoin white paper on 31 October 2008 and released version 0.1 of the software on 9 January 2009.
How it works
It chains cryptographically hashed blocks of transaction data. Each block contains a hash of the previous block, a timestamp, and transaction data. Nakamoto added a Hashcash-like proof-of-work mechanism and a difficulty parameter to regulate block creation rate.
Blocks hold batches of transactions hashed into a Merkle tree. Separate blocks can be produced at the same time, creating a temporary fork, so each peer keeps the highest-scoring version of history it knows; bitcoin treats the chain with the most cumulative proof-of-work as valid, and blocks not selected are called orphans. There is never an absolute guarantee that an entry stays in the best version of history, only that the probability of it being superseded falls exponentially as more blocks are built on top. Bitcoin’s average block time is ten minutes.
What works
The bitcoin blockchain reliably prevents double-spending. Its decentralised consensus works across untrusted nodes. The genesis block’s embedded timestamp proves immutability from day one.
Block 0 paid a reward of 50 bitcoins. Its embedded text cites a Times headline of 3 January 2009 about a second bank bailout, which has been read both as a timestamp and as a derisive comment on instability caused by fractional-reserve banking.
What does not
It does not scale for high-frequency transactions. It does not reduce computational cost: proof-of-work demands increasing energy. It does not eliminate coordination overhead—it replaces central authority with emergent, contested governance.
In June 2018 the Bank for International Settlements criticised public proof-of-work blockchains for their high energy consumption. A 2021 Cambridge study put bitcoin at 121 terawatt-hours a year, more electricity than Argentina and the Netherlands (109 terawatt-hours). Ethereum moved from proof of work to proof of stake in September 2022, and researchers have estimated that bitcoin uses 100,000 times as much energy as proof-of-stake networks. As the data to be processed grows, the computing resources needed become more expensive, which risks centralisation.
What it changes
It changes how digital records can be verified without intermediaries. It establishes a new baseline for public, append-only, tamper-resistant ledgers. It shifts trust from institutions to code, cryptography, and collective verification.
Nakamoto’s identity is unknown; the name is pseudonymous and may stand for more than one person. Whether private, permissioned systems deserve the name is still argued: proponents say a carefully designed permissioned chain can be more decentralised in practice, while critics say many in-house blockchains will be nothing more than cumbersome databases.
Is it worth your time
Yes—if you work on distributed systems, consensus protocols, or digital trust models. No—if you need high throughput, low latency, or energy-efficient recordkeeping.
