From zero to Ethereum · 01 / 01

From Reading Information to Verifying Value Together

Web1, Web2, and Web3 are not three versions that replaced one another overnight. They are overlapping ways of organizing the web: who publishes information, who records the facts, and who sets the rules.

  • Difficulty: Beginner
  • Reading time: About 35 minutes
  • Diagrams: 5
  • Self-test: 4 questions
The test for this lesson

The difference is not how the page looks. It is who has the final say over the records that matter.

Once you have this frame of reference, blockchain, wallets, smart contracts, and Ethereum become more than slogans.
Lesson contents
  1. 00 · Build the frame
  2. 01 · Three Web eras
  3. 02 · The Information Web
  4. 03 · The Platform Web
  5. 04 · The Value Web
  6. 05 · One digital item
  7. 06 · Hybrid systems
  8. 07 · Summary and self-test
00

Build the Frame of Reference

Before discussing Web1, Web2, and Web3, separate two terms that are often confused: the Internet is the infrastructure; the Web is the system of information and applications that runs on top of it.

Internet

The Internet

A “network of networks” made up of fiber-optic cables, routers, computers, and protocols such as TCP/IP. It allows different devices to exchange data.

World Wide Web

The Web

The space of information and applications that runs on the Internet, usually accessed through URLs, HTTP, HTML, and web browsers.

Email also uses the Internet, but email is not the Web. Likewise, Web1, Web2, and Web3 are not three versions of TCP/IP, and none has an official worldwide release date. They are conceptual labels that help us examine how online applications have evolved. ethereum.org also presents these periods as broad teaching categories and notes that Web3 has no single, rigid definition.[3]

Web usage models Web1 / Web2 / Web3: how publishing, interaction, control, and record-keeping are organized
Web technologies Browsers, URLs, HTTP, HTML, JavaScript, and application services
Internet Connectivity, routing, TCP/IP, and the physical infrastructure that carries data
Figure 01Web1, Web2, and Web3 describe the top layer: patterns of use and organization. All three still rely on the web technologies and Internet infrastructure beneath them.

Three Questions to Ask About Any Online Product

01

Who can publish?

Are ordinary users limited to reading, or can they create, interact, and deploy their own programs?

02

Who keeps the authoritative record?

Do the facts live on one server, in one company's database, or in state verified by many participants?

03

Who can change the rules?

Who can ban an account, change a balance, revoke access, or upgrade the rules the system executes?

Core question

The deepest difference among the three Web eras is not the three verbs “read, write, own.” It is this: who records the facts in the system, and what guarantees users’ rights?

01

Three Generations of the Web—Not Three Replacements

The most common mnemonic is: Web1: read; Web2: read and write; Web3: read, write, and own. It is useful—but only with careful qualifications, so that history does not collapse into a slogan.

  1. 01 Information Web

    Web1 · Read

    Sites publish content and visitors primarily read it; open protocols and hyperlinks let information flow around the world.

    User role
    Primarily a reader
    Source of truth
    Website server
    Core value
    Open distribution
  2. 02 Platform Web

    Web2 · Read and write

    Users create, socialize, and transact; large platforms package accounts, recommendations, payments, and data into accessible services.

    User role
    Participant
    Source of truth
    Platform database
    Core value
    Scale and usability
  3. 03 Verifiable Web

    Web3 · Verify

    Wallets, blockchains, and smart contracts seek to prevent key state from being determined by a single platform alone.

    User role
    Users initiate; nodes verify
    Source of truth
    Protocol and consensus
    Core value
    Verifiable control

The arrows represent capabilities accumulating over time, not one generation deleting the last. Many Web1-style personal sites still exist today. Web2 platforms remain a dominant part of the Internet. And most Web3 applications still use browsers, cloud services, and the interaction patterns and user experience associated with Web2.

Dimension Web1 Web2 Web3
Primary activities Reading, browsing, and following links. Creating, interacting, collaborating, and transacting. Signing transactions, verifying state, holding assets, and making programmable exchanges.
Identity and access Visitors or simple accounts. Platform accounts and social logins. Wallet addresses and verifiable credentials.
Authoritative record Pages and files stored on the site's server. A platform database controlled by a company. Onchain state collectively verified under public rules.
Payment rails Usually relies on channels outside the Web. Integrates banks, card networks, and payment platforms. Protocol-native assets and settlement.
Main advantage Open standards, independent sites, and free linking. Usability, efficiency, real-time interaction, and scale. Open participation, verifiability, and composability.
Main trade-off Higher barriers to publishing and interaction. Accounts, data, and rules are centralized. Key-management responsibility, fees, performance constraints, and governance complexity.
02

Web1: Information Can Flow Freely

The dominant pattern of the early Web was simple: site operators published pages, visitors read them in a browser, and hyperlinks led from one independent site to another.

Tim Berners-Lee proposed the World Wide Web at CERN in 1989, then helped build its early server, browser, and core specifications. URLs, HTTP, and HTML gradually became open standards, allowing independently operated sites to connect into a global information space.[1][2]

The “read-only Web” is a summary of the dominant experience, not a technical prohibition. Guestbooks, forms, forums, chat rooms, and e-commerce all existed early on. The real difference is that most ordinary users were not yet continuous contributors on large platforms, and interactive features had not been packaged into standardized services as they are today.

CreatorBuilds and uploads pages
Independent websiteThe server stores files; URLs provide addresses
ReaderBrowses, reads, and follows links
Figure 02The Web’s underlying protocols are highly open: in principle, anyone can create a site. But each site's content is still controlled by its own server and operator.

Why Call It the “Information Web”?

The defining property of digital information is that it can be copied without consuming or altering the original. You can send an article to one hundred people without losing your own copy. The Web drove the cost of copying, finding, and distributing information dramatically lower—a profound advance for open knowledge.

But that same property reveals another problem. If a digital object must remain scarce, or be spent by only one person, copying a file cannot by itself express a transfer of control. Information networks are good at answering “What is this content?” They do not inherently answer “Who controls it now?”

Analogy · A digital library

Web1 is like a global digital library: open protocols connect many bookshelves, but that model provides no internet-native system of property rights and settlement.

03

Web2: Platforms Organize Participation

Web2 turned ordinary users from readers into active participants. Posting, commenting, liking, uploading videos, shopping, hailing rides, collaborating at work, and playing online games all became part of daily life.

Platforms solved a long list of difficult problems for users: account management, data storage, content moderation, search and recommendations, instant messaging, payment integration, spam protection, and password recovery. By delivering a stable, convenient, end-to-end experience, they created enormous network effects.

Creator
Consumer
Merchant
Developer
Platform service
account: user_123
followers: 8,420
balance: 100
access: allowed
Figure 03Users may appear to interact directly, but platform servers typically execute the business logic, while platform databases store accounts, relationships, balances, and permissions.

This makes the platform database the system’s ultimate source of truth. Your 8,420 followers on a social network or 100 gold coins in a game are, technically, usually records in a company’s database. Under its terms of service, the platform can change its interfaces, reorder results, restrict transactions, suspend accounts, or discontinue the service.

What we gain

Efficiency and convenience

Low barriers to entry, high throughput, privacy controls, content moderation, customer support, and account recovery let billions of people participate safely and conveniently.

What we delegate

Ultimate control

Platforms usually control identities, data, recommendations, payment interfaces, and access rules unilaterally. Users can rarely leave with their complete relationships and records intact.

Centralization is not inherently malicious. It is an organizational model that uses a clearly identified operator and a unified database to gain speed, accountability, and ease of use. What matters is recognizing the exchange: you receive a service, and you also give its provider final authority over the records.

Analogy · A large shopping mall

Web2 resembles a well-run shopping mall: it is easy to set up shop and reach customers, but the operator owns the membership system, the premises, and the rules of business.

04

Web3: Key State Can Be Verified Collectively

Web3’s central experiment is not to give websites a new look. It is to keep certain key records from existing solely in one company’s database.

In this course, Web3 means the Web in a blockchain context: users initiate and authorize actions, while nodes in a network apply public rules to determine whether records may be updated. Later lessons on cryptography, transactions, and blockchains will explain how authorization, verification, and consensus work in practice. The term remains contested, and it should not be confused with “Web 3.0” or the Semantic Web—the W3C usage associated with machine-readable data.[4]

First, understand “state”

State is the set of relevant records a system recognizes at a given moment—for example, balances, controllers, or membership status. A valid action does not send a physical object through a cable. It updates the records the system recognizes from “before the action” to “after the action.” For now, this intuition is enough; transaction structures and cryptographic details can wait.

Previous state S
Authorized action Alice → Bob · 3 Later lessons explain authorization and verification
New state S′
Figure 04This diagram makes one point: instead of being updated privately by a single platform, key records can be checked and accepted by network participants under shared rules.

What does “value” mean in the “Value Web”?

Here, value means more than market price. It broadly includes digital rights and entitlements that can be explicitly controlled, transferred, verified, and programmed: native assets, tokens, memberships, game items, claims, lending positions, or voting rights.

01

Identifiable

The system can clearly distinguish the object, its quantity, and its current state.

02

Has a controller

Public rules can determine who is entitled to authorize the next action.

03

Protected against double-spending

Copying data does not also copy the control recognized by the protocol.

04

Transferable

A valid transaction can update the system’s state so control moves from one party to another.

05

Verifiable

Third parties can inspect key records without needing access to a platform’s internal systems.

06

Programmable

Transfers and use can carry conditions that code executes automatically.

Three qualifications to “ownership”

  • Protocol control is not legal ownership. Controlling a token does not automatically grant copyright in an associated image, property rights in a physical object, or any associated legal status.
  • Protocol control is not absolute security. Users can still lose access through mistaken approvals, software flaws, or service failures. Later security lessons will examine these risks.
  • Onchain does not mean fully decentralized. A product may still entrust its website, operations, and substantial business data to centralized services.
Trust, restructured

Web3 does not eliminate trust. It attempts to make key rules public, verifiable, and resistant to unilateral changes by a single operator.

05

One Digital Item, Three Models of Control

Imagine earning a “golden sword” in an online game. It may look identical on screen, yet the real control relationship changes completely depending on the system behind it.

Web1 · Display

You can see it

A webpage presents the image, attributes, and story; the server provides the information.

  • Record: website files
  • You can: read and download the image
  • Key issue: no independent ownership state
Web2 · Use

Your account has permission to use it

A company database assigns the item to your game account.

  • Record: platform database
  • You can: use or trade it under the game’s rules
  • Key issue: the platform retains final authority to change the record
Web3 · Verify

An address controls the onchain record

A smart contract records your address as the token’s controller, and transferring it requires authorization.

  • Record: contract and shared state
  • You can: authorize transfers and let compatible applications read the record
  • Key issue: compatibility, legal, and smart-contract risks remain

Even if the third model is fully implemented, the sword does not automatically work in every game. Another system must still understand its standard, artwork, statistics, and gameplay. A portable protocol record does not create product compatibility by itself.

The image itself also remains copyable. A blockchain can establish which address controls which token within protocol state; it does not make the image impossible to copy or automatically determine copyright ownership.

06

Real-World Applications Are Usually Hybrid Systems

Real products rarely belong to only one generation of the Web. They often combine open webpages, platform services, and shared networks, so you must keep asking which layer holds each key record.

Open Web

Browsers, links, and public information

Inherited from Web1
Platform Services

Accounts, search, recommendations, notifications, and large files

Inherited from Web2
Shared Records

Key state that multiple participants must verify together

What Web3 attempts
Figure 05One product can contain all three structures. Web3 can add a layer of jointly verifiable records to the existing Web; it does not erase the network beneath it.

Web3 applications still use the open protocols established by Web1 and draw heavily on Web2 interaction patterns, cloud services, and product design. They do not build a separate internet from scratch; they add new coordination layers—such as wallets, blockchains, and smart contracts—on top of the existing network.

Six Common Misconceptions

Myth 01“Web1 had no interaction at all—only static text.”
More accurate“Read-only” describes the dominant user role. Forms, forums, and commercial services already existed, but interaction was not yet packaged at platform scale.
Myth 02“Web2 is inherently evil, and centralization has no value.”
More accurateCentralization can provide performance, usability, privacy controls, moderation, recovery, and clear accountability. Concentrated control also creates dependence.
Myth 03“If a website says ‘blockchain,’ it must be fully decentralized.”
More accurateThe label is not decisive. Check who controls and can change the key records, rules, and access points.
Myth 04“Web3 is just token prices, NFT images, or the metaverse.”
More accurateThose are only some applications. The deeper subject is how digital state can be authorized, verified, transferred, and programmed.
Myth 05“Anything recorded on a blockchain must be true in the real world.”
More accurateA shared network can verify that its internal records changed according to its rules. External facts such as weather, prices, or identity still depend on data sources.
Myth 06“Web3 will completely replace Web2.”
More accurateAll three structures are likely to coexist for a long time. Putting state onchain may be worthwhile when multiple parties need shared facts, open participation, or less dependence on a single controlling party.
One sentence

Web1 expanded access to information. Web2 expanded participation. Web3 attempts to expand verifiable control and coordination.

07

The Entire Lesson as One Chain of Reasoning

Do not memorize three labels in isolation. Follow the question “Who records the facts?” and you can see why studying Web3 leads us to blockchains and Ethereum.

  1. The Web first connected information

    Open standards and hyperlinks let independent sites publish, copy, and connect content for a global audience.

  2. Platforms then enabled participation at scale

    Unified accounts, databases, and services made creation, collaboration, payment, and real-time interaction easy.

  3. Convenience introduced new dependencies

    Key accounts, relationships, balances, and rules became concentrated in platform databases, where the platform retained final authority to change them.

  4. Web3 changes the source of key state

    Signatures, blockchains, and smart contracts allow some records to be jointly verified by many participants under public rules.

  5. Ethereum asks the next question

    Can a publicly verifiable shared ledger be extended into a publicly verifiable state machine that executes general-purpose rules?

The lesson’s final answer

Web1 let information circulate openly. Web2 let platforms organize interaction efficiently. Web3 attempts to let actions over digital rights and key state be authorized under public rules, with the resulting state verified and made programmable on open networks.

Four-Question Self-Test

1. A service lets anyone inspect its code, but user balances exist only in a company database. Which control model does it most closely resemble?

2. Users sign in with a wallet, but order and asset records still exist only on company servers. Which assessment is most accurate?

3. Will Web3 make Web1 and Web2 completely obsolete?

4. When you transfer money with a banking app, where is the change in value ultimately recorded?

Essential Glossary

Internet
The infrastructure and suite of protocols that connect different devices and networks.
Web
The information and application space that runs on the Internet and is typically accessed through a browser.
Database
A system for storing, querying, and updating organized data. In a typical Web2 platform, the operator has final write authority.
State
The set of relevant facts a system recognizes at a given moment. A transaction transitions the system from an old state to a new state.
Web3
A contested family of concepts. In this lesson, it specifically means network applications that use blockchains, wallets, and smart contracts to create verifiable shared state.

Lesson complete

The real dividing line is who can authorize, verify, and govern the state the system recognizes—and under what rules.

01 / 02 The Problems of the Traditional InternetNext: concentrated data and control, dependence on central institutions, and a highly centralized financial system

Sources and Further Reading

  1. W3C: History of the Web — The birth of the World Wide Web and the history of its early servers, browsers, and open standards.
  2. CERN: Where the Web was born — The Web’s origins at CERN and its release as an open technology.
  3. ethereum.org: What is Web3? — Broad periodizations of Web1 and Web2, plus the core principles and limitations of Web3 in the blockchain context.
  4. W3C Linked Data Glossary — The use of “Web 3.0” in the Semantic Web and machine-readable data context, included to distinguish the terminology.
  5. Ethereum Whitepaper — The original design motivation for extending a digital-asset ledger into a general-purpose state-transition platform. It is useful historical context, not a complete description of today’s protocol.