A Ledger Everyone Shares

Picture the accounts book of a small village shop. One book, one owner, one handwriting. If the shopkeeper writes down that you paid, you paid. If they cross it out, you did not. Everyone in the village has to trust that one book — and, really, that one person.

A blockchain replaces that single book with thousands of identical copies, held by thousands of unrelated people, that update together. To change what the book says, you would have to change most of the copies at once, in front of everybody, faster than they can notice.

What that buys you

• No single owner. There is no shopkeeper who can quietly amend the page.
• No single point of failure. Copies can go offline and the record survives.
• Anyone can audit it. The whole history is public and readable by anyone.

What it costs you

These are not free wins, and the rest of this course is largely about the price. Keeping thousands of copies in agreement is slow and expensive compared to one database. Nothing can be undone: a mistaken payment has no support line to call. And "no owner" means no one is obliged to help you when something goes wrong.

A blockchain is not a faster database. It is a slower, costlier database that removes the need to trust whoever runs it. If you already trust them, you do not need one.

Hold on to that trade-off. Every design decision in the lessons ahead — how blocks are chained, how the network agrees, why fees exist — is someone paying that cost on purpose.