From Ledgers to Blockchains: A Short History of Trust

What Is a Ledger?

A ledger is simply a record of transactions. It answers one question over and over: who owns what? Your bank statement is a ledger. So is the notebook a shopkeeper uses to track who owes them money. Even your phone's contact list is a kind of ledger (a record of who you know).

The important part is not the paper or the database — it is the agreement. A ledger only works if everyone involved trusts that the records are accurate and complete. That is why ledgers and trust have always travelled together.

A Very Short History of Record-Keeping

1. 1

   c. 3000 BCE — Clay tablets in Mesopotamia

   Sumerian scribes pressed marks into clay to record grain, livestock, and debts. These are among the earliest known ledgers — and they were kept by temple and palace officials, not by the public.

2. 2

   c. 5th century BCE — Coins and public records

   Lydia (in modern Turkey) minted some of the first coins. Governments and temples began keeping official registers of taxes and payments, reinforcing the link between ledgers and state power.

3. 3

   1494 — Double-entry bookkeeping

   The Italian mathematician Luca Pacioli published a famous description of double-entry bookkeeping. Every transaction is recorded twice — once as a debit and once as a credit — making errors and fraud much easier to spot. This is still the backbone of modern accounting.

4. 4

   20th century — Digital databases

   Banks moved their ledgers onto computers. Records became faster, larger, and easier to search — but they were still controlled by a single institution.

5. 5

   2008 — Bitcoin

   Satoshi Nakamoto published a nine-page paper describing a peer-to-peer electronic cash system: a ledger maintained by thousands of computers, with no central owner. The first block was mined in January 2009.

The Trust Problem with Centralised Ledgers

Centralised ledgers are not bad — they are efficient and have powered economies for centuries. But they come with a built-in weakness: you have to trust the keeper.

That trust has three costs:

1. Single point of failure. If the bank's database is corrupted, hacked, or destroyed, the records can vanish. You are left with no proof of your money.
2. Power to alter history. The keeper can change entries — accidentally or deliberately. A bank can freeze an account; a company can rewrite its books; a government can seize assets.
3. Verification by permission. You cannot independently check that the ledger is complete. You rely on audits, statements, and the keeper's word.

In short, centralised ledgers concentrate both efficiency and risk in the same place.

Enter Bitcoin: A Ledger Nobody Owns

In October 2008, a paper titled Bitcoin: A Peer-to-Peer Electronic Cash System was posted to a cryptography mailing list. Its author, Satoshi Nakamoto, proposed a way to keep a shared ledger without a central keeper.

The core idea is simple to state and hard to achieve:

• Everyone can hold a copy. Thousands of computers (nodes) each keep a full copy of the transaction history.
• Transactions are grouped into blocks. Each block contains a batch of transactions and a cryptographic link to the previous block.
• The chain is the ledger. Because each block points back to the one before it, changing an old record would require redoing all the work that came after it.
• New blocks are added by competition. Miners race to solve a computational puzzle (proof of work). The winner proposes the next block, and the network checks it.

Notice what is missing: no bank, no company, no government deciding what is true. The ledger's truth is enforced by cryptography and consensus rules that every participant can check.

Centralised vs Distributed Ledgers

A Tiny Taste of the Code

You do not need to be a programmer to understand blockchains, but seeing a few lines of Python helps demystify the idea. The snippet below shows the essence of a block: it stores some data, the hash of the previous block, and its own hash. Change the data, and the hash changes — which is exactly why tampering is detectable.

import hashlib
import json

class Block:
    def __init__(self, index, data, previous_hash):
        self.index = index
        self.data = data
        self.previous_hash = previous_hash
        self.hash = self.compute_hash()

    def compute_hash(self):
        block_string = json.dumps({
            "index": self.index,
            "data": self.data,
            "previous_hash": self.previous_hash
        }, sort_keys=True).encode()
        return hashlib.sha256(block_string).hexdigest()

# Build a tiny chain
block0 = Block(0, "Genesis block", "0" * 64)
block1 = Block(1, "Maria pays Ali 6 coins", block0.hash)
block2 = Block(2, "Ali pays Ben 2 coins", block1.hash)

print("Block 1 hash:", block1.hash)
print("Block 2 previous:", block2.previous_hash)
print("Chain intact?", block2.previous_hash == block1.hash)

# Now tamper with block1 and see what happens
block1.data = "Maria pays Ali 600 coins"
block1.hash = block1.compute_hash()
print("After tampering, chain intact?", block2.previous_hash == block1.hash)

Why This Matters Beyond Money

The leap from centralised to distributed ledgers is not just about cryptocurrency. Anywhere records need to be shared between parties who do not fully trust each other, a distributed ledger can help:

• Supply chains — proving where a coffee bean or a diamond came from.
• Land registries — reducing disputes over who owns a plot.
• Digital identity — letting people control their own credentials.
• Voting and governance — making results independently verifiable.

Each of these has real trade-offs (speed, cost, privacy, regulation). But the underlying idea — a shared record that no single party can quietly rewrite — is genuinely new in the long history of ledgers.

We have proposed a system for electronic transactions without relying on trust.