The Web3 Book
Contents
Preface

Preface: How to Read This Book

This book attempts something that is harder than it may first appear: to answer a single question — What is Web3? — with genuine depth and rigour, while remaining genuinely readable by someone who has never written a line of code, set up a "wallet," or thought hard about how the internet works. Most writing on this subject picks one audience and abandons the other. Technical literature assumes you already understand hashing, consensus, and public-key cryptography. Popular writing assumes you do not, and so skips the very details on which every serious claim about Web3 actually depends. This book refuses both shortcuts. It is written on the conviction that an educated, curious person can understand this material properly — not in caricature — if it is built up patiently and in the right order.

The dual aim, and how the book honours it

The tension between rigor and accessibility is real, but it can be managed rather than split the difference. In this book, rigor lives in the argument and the evidence: claims are supported by citations to real sources; competing positions are presented in their strongest form before being weighed; technical terms are defined precisely; and the limits of what can honestly be claimed are stated plainly. Accessibility lives in the prose: nothing is left as unexplained jargon, sentences aim for clarity rather than ornament, and any idea that would normally be expressed in mathematics is instead described in words.

Several deliberate devices serve the reader. The first is define-before-use: the first time a technical term appears, it is set in bold, given a plain-language definition, and paired with a concrete real-world analogy. Because analogies can mislead as easily as they illuminate, each one is followed, where it matters, by a note on exactly where the analogy breaks down — so that a simplification never hardens into a falsehood. The second device is a recurring restatement, marked throughout the text like this:

In plain terms: after any dense or technical passage, you will find a short paragraph like this one that says the same thing again in everyday language. If a section's argument feels slippery on first reading, find the next "In plain terms" note and start there.

The third support is a Glossary in the back matter, which collects every key term with a one-line definition, so that a concept introduced in an early chapter can be refreshed later without hunting back through the text. Together these devices are not decoration; they are the mechanism by which the book tries to keep its promise to two audiences at once.

How different readers might use this book

The book is built to be read straight through, and a reader who does so will get the fullest version of its argument. But it is long by necessity, and not everyone needs all of it. A few suggested paths:

  • The curious newcomer who simply wants orientation can read Part I (the framing of the question), Part II (the history of the web that sets up why anyone proposed an alternative), and then skip to the Conclusion (Chapter 35). This gives the story and the verdict without the full technical machinery in between.

  • The reader who just wants the answer — a working definition of Web3 and a considered judgement about its claims — can go directly to Chapter 25, Toward a Definition, and Chapter 35, Conclusion. These two chapters are written to stand largely on their own, with cross-references back to the supporting material for anyone who wants to check the reasoning.

  • The reader who wants to understand the technology rather than take it on faith should not skip Part III (cryptography, distributed systems, blockchains, Bitcoin, Ethereum, consensus). These chapters are the conceptual heart of the book, and the later assessment of Web3's claims rests on them. They are also the chapters most carefully written for someone without a computing background; Chapter 2, A Reader's Primer, builds the groundwork from the very beginning — what a server is, what "the cloud" means — and assumes nothing.

  • The reader interested in the stakes rather than the mechanics — the politics, the money, the law, the harms and the hopes — will find the most relevant material in Part V (Web3 as ideology, and the crucial distinction between Web3, the Semantic Web, and the metaverse) and Part VI (use cases, critiques, externalities, regulation, and security).

Cross-references throughout point between chapters so that any path can be followed without getting lost, and so that no concept has to be explained twice.

On citations and sources

This is a work of scholarship, and its authority rests on its sources. It uses author–date citations in the text — for example (Nakamoto, 2008) or (Wood, 2014) — with full references gathered at the end of each chapter and consolidated in the master bibliography in the back matter. A reader new to this convention can safely treat the parenthetical names and dates as signposts: they indicate that a claim rests on a specific, traceable source, which can be looked up and checked. One commitment is worth stating explicitly, because the field around Web3 is unusually prone to confident assertion without evidence: every source cited in this book is real and verifiable. No author, title, statistic, quotation, or web address has been invented. Where the available evidence is thin, contested, or merely anecdotal, the book says so rather than dressing up a guess as a finding.

What to expect in tone

The reader should expect even-handedness, and should hold the book to it. Web3 attracts two equally unhelpful styles of commentary: uncritical promotion, which treats every claim as already proven, and reflexive dismissal, which treats the whole enterprise as obviously fraudulent. This book does neither. It presents the strongest version of the proponents' case and the strongest version of the critics' case, and then weighs them against the evidence. Where Web3 has produced real innovation, that is said clearly. Where its rhetoric outruns what has actually been demonstrated, that is said equally clearly. The aim is not to persuade the reader to adopt Web3 or to reject it, but to equip the reader to think about it well. This book does not offer financial advice, and discussions of tokens, decentralized finance, and related instruments are analytical, never recommendations.

A note on scope and timing

Finally, two honest limits. First, scope: this book answers one question — what Web3 is — and not the many adjacent questions it could have chased ("how do I build an application?", "which token should I buy?"). That discipline is what keeps a large book from becoming an unfocused encyclopedia. Second, timing: Web3 is a fast-moving and still-young phenomenon, and this book is a snapshot taken in the mid-2020s. Particular projects, prices, regulations, and technical details will date quickly. The book is therefore built to age as gracefully as possible by emphasizing the durable structure — the concepts, the arguments, the ideology, and the pattern of claim and evidence — over the ephemeral specifics. A reader years from now should still find the framework useful for making sense of whatever "Web3" has by then become.

With that, we turn to the question itself.