The one-sentence definition
A blockchain is a ledger that is maintained by many participants, appended in time order, and whose history is very hard to alter. The problem it solves is specific: how do mutually distrusting participants agree on one ledger?
The traditional answer is a central institution that keeps the books and is trusted by everyone. A blockchain hands that to rules and incentives: nobody owns the ledger, but anyone who follows the protocol can verify it.
Blocks and hashes
A block usually has three parts:
| Part | Content | Purpose |
|---|---|---|
| Header | Previous block hash, timestamp, difficulty target, Merkle root | Binds the block to history and summarises all transactions |
| Transaction list | All transactions in the block | The actual ledger changes |
| Metadata | Version, nonce and similar | Used by the consensus algorithm |
The key is the hash pointer: each header records the previous block's hash. Change one transaction in block 100 and its hash changes; the hash recorded in block 101 no longer matches and the chain breaks. Hiding the change means recomputing every later block.
Transactions are organised in a Merkle tree: pairs are hashed, then hashed again upward until a single root remains. Comparing roots is enough to tell whether the transaction set changed.
Consensus
The network must agree on who produces the next block and which chain is canonical. Two schemes dominate:
Proof of work (PoW)
Miners repeatedly try nonces until the block hash meets a difficulty target. Finding the solution takes real computing power; verifying it takes one calculation. To rewrite history an attacker needs more than half the hash power, which is very expensive. The cost is energy use and hardware.
Proof of stake (PoS)
Validators stake assets for a chance to produce blocks, and misbehaviour is penalised by slashing the stake. Energy use falls sharply, but it raises questions about stake concentration and "the rich get richer". Ethereum moved from PoW to PoS in 2022.
| Dimension | Proof of work | Proof of stake |
|---|---|---|
| Basis for block production | Computing power | Staked assets and random selection |
| Energy use | High | Low |
| Cost of attack | Sunk hardware and electricity | Stake is slashed |
| Main criticism | Energy consumption | Stake concentration and access |
Three chain types
- Public chains: anyone can read and participate in validation, as with bitcoin and Ethereum. Most decentralised, usually least throughput.
- Consortium chains: maintained by a known group of institutions with permissioned access. Common in clearing and supply chains; efficient, but with a different trust model.
- Private chains: controlled by one organisation, closer to a traditional database with an audit log, and only lightly decentralised.
None is universally better; the right choice depends on the trust model a use case needs. Marketing a private chain as "decentralised" is a common confusion.
What it cannot do
Limits are more useful to understand than advantages:
- It cannot guarantee that on-chain data is true. The chain guarantees the record was not altered, not that the input was honest.
- It does not protect privacy by default. Public ledgers are open, and addresses can be linked to identities through analysis.
- It cannot scale without limits. Decentralisation, security and throughput trade off against each other — usually called the "blockchain trilemma".
- It cannot enforce real-world promises. A smart contract can move on-chain assets; it cannot compel performance offline.
- It cannot eliminate human error. A wrong address or a lost key is beyond the chain's help.
Real uses
Beyond cryptoassets, four uses are relatively mature: cross-border settlement (shorter clearing chains), asset registry and notarisation (timestamps and tamper resistance), supply chain traceability (all parties share one ledger), and automatic execution via smart contracts (settlement when conditions are met).
All four share three traits: the parties do not trust each other, they need one shared state, and auditing matters. Where those do not apply, an ordinary database is usually cheaper.
For how this applies to assets, see what is cryptocurrency; for custody, see how to set up a crypto wallet.