This chapter is the hinge of the book. Everything before it has assembled materials — the history of the web (Part II), the cryptographic and distributed-systems machinery (Part III), and the components that machinery makes possible (Part IV). The task now is to convert those materials into an answer to the question the title poses. We do this not by decreeing a definition but by laying the major competing definitions side by side, examining what each one chooses to emphasize and what each one quietly leaves out, and then proposing a synthesis that the remaining chapters will test. The chapter establishes a deceptively simple but consequential claim: there is no single definition of Web3 because the people who define it want the word to do different jobs. To define Web3 well, one must first map the disagreement.
We begin with the slogan most readers will already have met — "read, write, own" — and treat it not as the answer but as the entry point.
In plain terms
the slogan says that in the first web you could only read what others published; in the second web you could read and write — post, comment, upload — but on platforms someone else owned; and in the coming third web you can read, write, and own — hold a real, transferable stake in the networks and content you use. Each word adds a new capability without removing the previous ones.
the catchy three-word history most people now use to explain Web3 was popularized by an investor whose firm had placed large bets on Web3 succeeding. That does not make the framing wrong, but it does mean it was authored by an interested party — a salesman as well as an analyst — and should be read with that in mind.
"read, write, own" is an excellent slogan and a flawed history. It teaches the core idea quickly, but it tidies up a messy past, treats a hoped-for future as if it had already arrived, and quietly picks one of several competing definitions — ownership — as the official story.
the foundation Wood created kept his distrust of intermediaries but added a moral vocabulary — fairness, and people controlling their own data, identity and destiny. The definition has begun to drift from a narrow security goal toward a broad promise about personal autonomy and justice online.
Ethereum's definition is the most "engineering-spec" of the four. It lists four properties a system must have to count as Web3: no central owner, no gatekeeper, money built into the network itself, and no need to trust a middleman. A reader can almost use it as a checklist.
Dixon's definition asks a single question — who gets to own the network? — and answers that Web3 lets the users own it, not just the company. Where Wood worried about trust and Ethereum.org listed properties, Dixon foregrounds money and power: the distribution of economic benefit.
all four people are pointing at roughly the same set of technologies — blockchains, tokens, cryptography — but each describes a different purpose as the essential one. For Wood it is escaping the need to trust institutions; for his foundation it is fairness and self-determination; for Ethereum.org it is a bundle of four technical properties; for Dixon it is who owns the value. The disagreement is not about the machinery but about what the machinery is for.
four different things can be called "the point" of Web3 — needing to trust people less, spreading out control, letting users own a stake, and paying people through tokens to keep the network honest. These overlap, but they are not the same, and which one you treat as essential decides which projects you count as "real" Web3 and which you dismiss as imposters.
much of what gives "Web3" its emotional force is not a precise picture of the new thing but a sharp reaction against the old thing. People often know with great clarity what they want to escape — being tracked, being deplatformed, having their data sold — more clearly than they know what they want to build. Web3 is, in large part, the name of that escape.
defining yourself by your enemy is powerful but risky. It gives a movement energy and a clear villain, but it also makes the label loose enough that anyone can claim it — and it offers no guarantee that the alternative will not, in time, come to resemble the original problem.
we are deliberately not saying "Web3 is blockchains" or "Web3 is decentralization." We are saying it is an ongoing attempt — using a particular family of technologies, animated by a particular set of beliefs, aimed at a particular target (platform power) — to rebuild the web around user control. It is a project with a toolkit and a creed, not a gadget.
the people selling Web3 tend to describe its purpose — no middlemen, user ownership, fairness — while waving at "the blockchain" as the means. Our definition does two things differently. It names the real means (cryptography, of which blockchains are one use, not the whole), so we can later check whether the machine delivers the mission. And it names the real goal (self-sovereignty — you control your identity, data, and value under rules you can verify), which turns out to contain the four rival definitions as special cases rather than competing with them.
What the chapter covers
- The canonical triad: read, write, own
- Four definitions on the table
- A comparison of the definitions
- Distinguishing the definitions by what they emphasize
- Web3 as defined by what it opposes
- A working definition
- Synthesis
Terms explained in this chapter
The full chapter is in the book.
Buy the full book