What is a Blockchain

1.1 — What is a Blockchain

Recall first (before reading). In one sentence, what problem do you think a “cash system without a bank” must solve that a normal database does not? Write it down. You’ll check it against §5.

Reference-book anchor

Primary reference: Blockchain Technology, Chapter 1, §§1.2–1.5 — converted Markdown lines 517–830.¹

Use this anchor for the book’s definition, transaction flow, P2P network, cryptographic trust, components, and block linkage. The explanations below preserve that foundation while separating permissionless assumptions from permissioned/enrichment examples.

Why this topic exists

Module I is the conceptual foundation. Before any hash function, Merkle tree, or consensus rule makes sense, you need a single, working definition of what a blockchain is and, more importantly, what job it does. Everything later in the course (Bitcoin, Ethereum, Hyperledger) is one answer to the question: “how do we keep a shared record that nobody alone controls?”

The one-line definition

A blockchain is a replicated, append-only ledger of transactions, organized as a chain of blocks, where each block cryptographically references the one before it, and a network applies a consensus protocol to agree on its contents. That network may be permissionless or permissioned; the trust model and participant roles differ.

Unpack the four load-bearing words:

Refresher — ledger vs. database. A ledger records events in order and is historically oriented (“who paid whom, when”). A general database answers queries (“what is Alice’s balance?”). A blockchain is a ledger first; balances are derived by replaying the ledger. This distinction explains why “just use a database” does not solve the trust problem.

The problem it solves: trusted third parties

In the traditional model, two strangers transact through a trusted intermediary (a bank, a payment processor, a land registry). The intermediary prevents double-spending and settles disputes. That works, but it has costs:

1. Single point of failure — the intermediary can be hacked, compromised, or coerced.
2. Rent extraction — the intermediary charges for the service.
3. Exclusion — the intermediary can refuse service.
4. Opacity — you trust the intermediary’s record; you cannot independently verify it.

Satoshi Nakamoto’s 2008 paper opened with this exact observation: “Commerce on the Internet has come to rely almost exclusively on financial institutions serving as trusted third parties to process electronic payments.”² A permissionless blockchain attempts to replace the intermediary with a publicly verifiable record and protocol. Permissionless means participation is generally open under protocol rules; it does not mean every participant stores a full copy or has every read, submit, validate, and govern role. A private or consortium chain still has trusted administrators or member organizations; it changes who must be trusted rather than eliminating trust entirely.

Four things to keep separate

These four layers are easy to blur in an exam answer:

A hash-linked file maintained by one company is tamper-evident data, but not automatically a decentralized blockchain. Replication, a participant model, validity rules, and a way to agree on ordering are what turn the data structure into a system.

How a transaction becomes history

A simplified flow is:

request → digital signature → peer-to-peer broadcast → validation
        → candidate block → consensus selection → replicated ledger

A signature proves control of a private key; it does not by itself prove that the transaction is valid, that the sender has not already spent the funds, or that the transaction is final. Those latter questions depend on the ledger state and consensus rules.²

The mental model: a shared notebook

Imagine a notebook passed around a room of strangers. Anyone may append a line (“Alice pays Bob 5”). The rules:

• Everyone has a copy.
• Nobody can erase or rewrite a line once written.
• A line is only accepted if it follows the rules (Alice actually had 5 to give).
• If two people append conflicting lines, the room uses an agreed rule to pick the “real” notebook.

That notebook is the blockchain. Cryptographic hashes and Merkle trees make later changes detectable; digital signatures authenticate control of a key; and the consensus protocol is the “agreed rule” for resolving conflicts.

What a blockchain is NOT

Beginners often over-attribute. Be precise:

• It is not inherently anonymous — a public chain is often pseudonymous (identities are addresses, not names), while a permissioned chain may bind addresses to verified organizations.
• It is not automatically fast or free — decentralization is a trade-off against throughput.
• It is not a database replacement for every use case — it is a specific tool for shared, contested record-keeping.
• Bitcoin (a currency) and “blockchain” (the data structure + protocol) are not the same thing. Blockchain is the substrate; Bitcoin is one application.

Worked example — “is this a blockchain?”

For each system, say blockchain or not, and give one reason.

1. A company’s internal PostgreSQL table of customer orders, backed up nightly.
2. A public file where anyone can append a signed message, and each message includes the hash of the previous message, maintained by a network that votes on ordering.
3. A Google Doc edited by 50 people with version history.

Answer (check after you commit):

1. Not — centralized, mutable, no consensus, no cryptographic chaining as a security property.
2. Blockchain — replicated, append-only, cryptographically chained, consensus on ordering.
3. Not — Google is the trusted central authority; edits are mutable; history is a convenience, not a tamper-evident consensus record.

Exercise

Name one real-world scenario not involving money where a blockchain’s properties (no trusted intermediary, tamper-evident history) would genuinely help, and one where a normal database is clearly better. Keep each to two sentences.

Exam lens

Definition to write: A blockchain is a replicated, append-only ledger whose blocks are cryptographically linked and whose participants use protocol rules to agree on valid history.

Do not confuse:

• A blockchain is a system; a block is one batch of records inside it.
• Encryption hides data; hashing provides a fixed-length fingerprint; digital signatures authenticate control of a key.
• Immutability means alteration is difficult to accept, not that the physical bytes can never be changed or that recorded real-world facts are automatically true.

Long-answer skeleton: start with the trusted-third-party/double-spending problem, define the ledger, explain replication and hash links, explain consensus, then state the trust-model trade-off and one case where a normal database is better.

Rapid revision

• Can I define blockchain without using the word “Bitcoin”?
• Can I name the roles of ledger, network, consensus, and application layers?
• Can I explain why a single-owner database is not automatically a blockchain?
• Can I distinguish pseudonymity, immutability, and finality?

Key takeaways

• Blockchain = replicated + append-only + cryptographically chained + consensus-governed ledger.
• Its job is to reduce dependence on a single trusted intermediary through verifiable data and protocol rules; permissioned systems retain selected authorities.
• Decentralization is a design choice that trades speed, control, and privacy for shared verification and resilience.
• “Blockchain” ≠ “Bitcoin”; the former is the substrate, the latter an application.

Sources