BR Academy
0%
What Is Blockchain?·Lesson 1 of 25·12 min

What Is Blockchain?

The Concept

A blockchain is a shared, append-only ledger of records — called "blocks" — that are cryptographically linked in sequence and copied across many independent computers (called nodes) instead of living on one company's server. Think of it as a spreadsheet that thousands of people each keep an identical copy of. Anyone can add a new row at the bottom, but no one can go back and quietly change a row that's already there, because every computer holding a copy would notice the mismatch instantly.

That's the whole idea in one sentence: blockchain trades "trust one company" for "trust math and replication."

In a traditional system — your bank's database, a social platform's server, a cloud provider's storage — one organization holds the master copy. You trust them to keep it accurate, to not alter your balance, and to still exist next year. A blockchain removes the single point of control. Instead of one copy, there are thousands of identical copies held by independent participants (nodes) around the world. Every new block of transactions is checked against the rules by many of these nodes before it's accepted, and once accepted, it's linked to the previous block using a cryptographic fingerprint (a "hash" — covered in detail in Module 2). Change anything in an old block and its fingerprint changes, which breaks the chain and is immediately visible to everyone holding a copy.

This is why blockchains are described as:

  • Distributed — no single server; thousands of independent copies.
  • Append-only — new data can be added, but existing data can't be silently edited.
  • Verifiable — anyone can check that their copy matches the network's copy.

None of this requires understanding cryptocurrency prices or trading. Blockchain is a record-keeping technology; cryptocurrencies are simply the first and most famous application built on top of it.

A useful mental model: picture a shared Google Doc where everyone in the world can see every edit, but no one — not even the document's creator — can delete or rewrite a past paragraph; they can only add new paragraphs underneath, each one stamped with a fingerprint of everything written before it. That stamping is what Module 2 covers in detail (hashing and block structure), but the intuition matters now: the history of a blockchain is append-only by design, not by policy. A company's terms of service can say "we won't edit your data," but that's a promise they could break. A blockchain's structure makes editing old data detectable by anyone, which is a much stronger guarantee than a promise.

It's also worth being precise about what "decentralized" means here, because the word gets overused. It doesn't mean "no one is in charge of anything" — networks still have rules (encoded in software that node operators choose to run) and processes for upgrading those rules. It means no single node, company, or person can unilaterally rewrite the ledger's history or block a valid transaction from inclusion, because doing so would require convincing or overpowering a large fraction of all the other independent participants. That's a meaningfully different kind of resilience than "the company promises to behave."

Worked Example

Imagine Alice sends Bob 1 unit of a cryptocurrency. Here's what happens, step by step:

  1. Alice's wallet software creates a transaction record: "Alice sends 1 unit to Bob," signed with Alice's private key (Module 3 covers keys in depth).
  2. This transaction is broadcast to the network and sits in a waiting area called the mempool alongside other pending transactions.
  3. A node (in Bitcoin, a "miner"; in many newer networks, a "validator") gathers a batch of pending transactions, including Alice's, into a candidate block.
  4. That candidate block includes a reference — a hash — pointing to the previous block in the chain, so it's cryptographically "stapled" to everything that came before.
  5. The network's consensus rules (Module 5) determine whether this candidate block gets accepted. Once accepted, every node updates its own copy of the ledger to include it.
  6. Alice's transaction is now part of the permanent, shared record. Bob's wallet shows the updated balance, and anyone in the world can independently verify the transfer happened by checking their own copy of the chain.

No bank authorized this. No single company's server went down and erased it. Thousands of independent copies agree, which is what makes the transfer final.

Exercise

Make a short list of three things you currently rely on a single company to do honestly on your behalf — for example, your bank (to report your balance correctly), a social media platform (to not quietly delete your posts or followers), or a cloud storage provider (to keep your files intact and accessible).

For each one, write a sentence answering: If this record were instead held as thousands of identical copies, verifiable by anyone, would that change how much I need to trust the single company? You don't need to conclude blockchain is better in every case — the goal is to notice where "trust one party" is doing invisible work in your daily life, and where a replicated, verifiable ledger could reduce that reliance.

As a second step, pick the one item from your list where replication would matter least, and write one sentence explaining why centralization is actually fine there (for example, a loyalty-points program you don't care about long-term, or a system where speed and easy error correction matter more than tamper-evidence). This half of the exercise matters just as much — blockchain is a tool for specific problems, not a universal upgrade, and being able to say "this doesn't need it" is as valuable a skill as recognizing where it helps.

Recap

  • A blockchain is a replicated, append-only, cryptographically linked ledger — not a database owned by one party.
  • Every node holds an identical copy, and new blocks must be accepted by the network's rules before they become permanent.
  • Blockchain is a record-keeping technology; cryptocurrency is just its first application.

Resources