From static pages to walled gardens

When Tim Berners-Lee first proposed the web in 1989, his vision was explicitly decentralized: remote machines would serve interlinked resources without any central control or coordination. The early web — Web 1.0 — delivered on that promise in the form of static documents served from distributed servers and read-only clients.

Web 2.0 shifted the paradigm. Interactive platforms replaced static pages, and network effects moved from hyperlink directories to engagement-driven services. The gains in usability and interactivity came at a cost: data and control consolidated in a handful of technology companies. The web drifted from its decentralized roots, where no central authority could block content or act as a single point of failure.

The decentralization blueprint of Bitcoin

Building a content platform that achieves decentralization at scale has proven difficult — with one notable exception. Bitcoin, introduced in a 2008 whitepaper by Satoshi Nakamoto, demonstrated that a peer-to-peer (P2P) network can run a public, consistent, tamper-proof distributed ledger without a central operator.

Several concepts underpin this achievement:

  • A peer-to-peer network is an architecture where each equally privileged node stores and relays information, eliminating single points of failure.
  • A distributed ledger is synchronized across computers via consensus, so each node holds a similar replica of the data.
  • A blockchain is a distributed ledger where data is stored in blocks cryptographically linked into an immutable, chronologically ordered chain.

Bitcoin’s network — over 40,000 nodes processing billions in transactions daily — proved distributed applications can operate securely at scale. That proof inspired programmable blockchains like Ethereum, where participants can deploy code that verifiably runs across all nodes. Today these blockchains host thousands of decentralized applications that remain available without reliance on any single entity.

Ownership and identity without intermediaries

Distributed systems differ fundamentally from centralized ones: neither data nor its processing is held by a single party. In a decentralized web, a content creator could host a blog across multiple locations operated by different entities, rather than depending on one platform whose outage would take down everyone’s content.

This model extends to identity. The cryptographic principles behind cryptocurrencies enable decentralized identity — a system where participants hold a secret key and use it to identify each other, without reaching out to a trusted third party as with OAuth 2.0. This allows selective data sharing and verifiable proof of past interactions. For instance, a college could issue a Decentralized Identifier (DID), letting students later prove their enrollment without contacting the institution. Projects such as ENS and Unlock build on this idea, using a blockchain as a shared source of trust for verifying identity and ownership.

The same principle drives NFTs: blockchain-based tokens convey ownership that can be publicly verified and updated. If the blockchain records that a public key controls an NFT, the holder can prove that ownership on any platform that recognizes the same chain.

Gateways to a distributed future

Decentralization and privacy are active engineering problems. Cloudflare has contributed to privacy-preserving protocols including Encrypted Client Hello (ECH), Oblivious DNS-over-HTTPS (ODoH), and OPAQUE, work that builds on the same zero-knowledge proof techniques used in distributed systems like ZCash and Filecoin.

Web3 projects such as Ethereum and IPFS run on their own architecture, still relying on the Internet but not on the traditional web stack. To bridge that gap, Cloudflare operates distributed web gateways that provide an HTTP interface to these protocols. This allows distributed content to be accessed securely without requiring experimental client software, easing the transition from the current web to a more decentralized one.

The earlier web was static; Web 2.0 brought interaction at the price of centralization. Web3 attempts to reverse that trade-off by building on open, distributed protocols that give participants control over their data and their identity.