Blockchain is one of the most hyped words in technology, and one of the least understood. Strip away the noise and it is a specific, clever answer to one question: how can a group of people who don't trust each other agree on a shared record, without a central authority in charge of it? This lesson explains what a blockchain actually is, why that property is genuinely useful, and — just as important — where it is the wrong tool. You will leave able to tell the real engineering from the marketing.
- Explain what a blockchain is in plain terms: a shared, append-only ledger
- Describe what 'decentralised' means and the problem it solves
- Identify what blockchains are genuinely good for — and what they are not
- Place the major eras (Bitcoin, Ethereum, Web3) in context
The one-sentence definition
A blockchain is a shared ledger — a record of transactions — that is copied across many computers, where new entries can only be added, never changed or deleted, and where the network agrees on what is true without any single party in charge. That is the whole idea. Every other feature builds on those three properties: it is shared (many identical copies), it is append-only (history is tamper-evident), and it is agreed by consensus (no central authority decides). If you hold just that sentence, you understand more about blockchains than most of the hype conveys.
Compare it to an ordinary database run by a bank. The bank's database is also a ledger, but the bank controls it: it can edit balances, reverse entries, or shut you out, and you simply trust it to be honest and available. A blockchain removes that central controller. No one owns the ledger; thousands of independent computers each keep a copy and follow the same rules, so no single one can rewrite history or block you. You trade the convenience of a trusted middleman for the guarantee that no middleman can betray you.
What 'decentralised' actually buys you
Decentralisation is the point, and it is worth being precise about what it gives you. Because the ledger lives on many independent machines, there is no single point of control or failure. No one can quietly change the record, because everyone else's copy would disagree. No one can censor a valid transaction, because they don't own the network. No one can switch it off, because there is no off switch to reach. And anyone can verify the whole history for themselves rather than trusting a report. These are real, valuable properties — for a currency no government can inflate at will, or a record no company can secretly alter.
The trade-off is always the same: decentralisation buys you censorship-resistance and tamper-evidence at the cost of speed, storage and simplicity. A central database is faster and cheaper. You only want a blockchain when removing the central authority is worth those costs.
A ledger you can picture
Think of the ledger as a running list of entries. Each entry says who sent what to whom. To make history tamper-evident, entries are gathered into blocks, and each block carries a fingerprint of the one before it, forming a chain (you'll see exactly how in a later lesson). Here is a simplified picture of what a couple of ledger entries and a block look like — not real blockchain data, just the shape of the idea.
{
"block": 1024,
"previous_block_fingerprint": "9f2c...a71b",
"transactions": [
{ "from": "Alice", "to": "Bob", "amount": 5 },
{ "from": "Bob", "to": "Carol", "amount": 2 }
],
"this_block_fingerprint": "3d81...54ee"
}Because each block references the previous block's fingerprint, changing an old transaction would change that block's fingerprint, which would break every block after it. To alter history you would have to redo all the work of every following block, on more than half the network at once — which the system is designed to make impractical. That is what 'tamper-evident' means in practice: not that history *can't* be changed, but that changing it is so costly and so obvious that no one can do it quietly.
What it's good for — and what it isn't
Being honest about the tool is what separates an engineer from a hype merchant. Blockchains are a genuinely good fit when several parties who don't trust each other need to share a record, and there is no neutral authority they all accept. Digital money that no central bank controls (Bitcoin), programmable agreements that run exactly as written without a company enforcing them (smart contracts), and provable ownership of a digital item are all real uses that flow directly from the core properties.
Equally important is knowing when *not* to reach for it. If one trusted organisation runs the system, a normal database is faster, cheaper and simpler — a blockchain adds cost for no benefit. If the data is private, a public ledger is the wrong place. And a blockchain cannot verify that real-world facts are true; it faithfully records whatever it is told, so 'put it on the blockchain' does not make bad data good. Many failed projects were a database wearing a blockchain costume. The skill is asking: *is there really no trusted party here?* If there is, you probably don't need a blockchain.
'Blockchain' is not a synonym for 'secure' or 'trustworthy'. It guarantees the ledger's integrity, nothing more. Garbage written to a blockchain is permanent, verifiable garbage. Always ask what problem decentralisation is actually solving before using one.
How we got here
A little history makes the landscape legible. Bitcoin (2009) was the first working blockchain: its single purpose is to be decentralised digital money, a ledger of who owns how many coins. Ethereum (2015) generalised the idea — instead of only tracking coin balances, its ledger can run small programs called smart contracts, making the blockchain a shared computer that anyone can deploy code to. That unlocked tokens, decentralised finance, NFTs, and the broad set of applications loosely called Web3: applications whose backend logic lives on a public blockchain rather than a company's servers.
This track follows that arc. These foundation lessons cover the ideas common to all blockchains — cryptography, blocks, consensus, wallets. Then the focus turns to Ethereum and Solidity, because that is where most smart-contract development happens and where you can most easily build and deploy your own contracts for free. By the end you will have written and shipped real ones. First, though, the machinery underneath: the cryptography that makes any of this possible, which is the next lesson.