A field guide to the decentralized internet
Distributed freely

Web5

Rebuilt from first principles

Web5 inherits from Web2 and Web3 to overthrow both. It wields Web2 technologies but rejects the Web2 paradigm. It stands on blockchains but builds off-chain, local-first.

The web does not have to be centralized services that every user connects to. Web5 is a network of equally connected nodes, each running its own stack: CKB node, Fiber node, your applications. No single point of failure. No single point of control.

// definition

What is Web5?

Web5 = Web2 + Web3. And Web5 is not Web2 + Web3. It takes what works from both and discards what doesn't.

web2.technologies

The parts that work

Mature user experience. Rich application ecosystems. High-performance infrastructure. Global network connectivity. Web5 uses these technologies, but rejects the Web2 paradigm of centralized control.

web3.sovereignty

The parts that matter

Decentralized consensus. Digital asset ownership. Permissionless innovation. Censorship resistance. Web5 stands on blockchains, but builds off-chain where computation belongs.

web5.synthesis

The local-first web

A mesh of PoW+UTXO consensus layers, channel networks, and P2P protocols. Each node runs its own stack. Local-first software connected into a local-first network through a trustless common knowledge base.

The term "Web5" was first used by Jack Dorsey in 2022 to describe a decentralized web built on Bitcoin. The CKB community expanded this vision beyond Bitcoin alone. The internet itself is already doing well. We just need P2P technology and cryptography to fix its problems. But the synthesis is not additive. Web5 inherits from both to overthrow both, arriving at something neither Web2 nor Web3 could be on their own.

// architecture

Web3 vs Web5

The differences are not cosmetic. They are structural, starting at the consensus layer and propagating through every design decision.

Dimension Web3 Web5
Consensus PoS (Proof of Stake) PoW (Proof of Work)
Data model Account model UTXO (Cell model)
Scaling Horizontal (Rollups, L2s) Vertical (state channels)
Topology Client → Server Peer ↔ Peer
Ownership Contract-custodied (second-class) User-held (first-class)
Computation On-chain execution Off-chain compute, on-chain verify
Privacy All transactions public Off-chain verification preserves privacy
Full node cost High (~2TB SSD for Ethereum) Low (~15GB for Bitcoin UTXO set)
Leader election Deterministic (MEV extraction) Non-deterministic (any node can mine)

PoS + Account model leads inevitably to client-server topology. Validator election is deterministic, creating MEV extraction. Global state makes full nodes expensive, forcing users to depend on centralized RPC providers like Alchemy and Infura. PoW + UTXO forms P2P topology naturally: leader election is non-deterministic, UTXO state is compact, and any node on commodity hardware can participate fully.

// philosophy

Core Pillars

Web5 is not just a technology choice. It is a set of beliefs about how the internet should work.

01

The Local-First Web

Local-first software has always been solitary, programs running on isolated personal machines. CKB changes this. A trustless common knowledge base and a peer-to-peer network connects isolated local-first software into a local-first network. Local-first social networks. Local-first payments. Local-first identity. Everything that used to require a centralized intermediary, without one.

Web 2.0 centralized services won because they required zero client-side setup. The tradeoff was giving up ownership, privacy, and performance. In the AI era, agents handle setup for you. The friction that kept local-first impractical is gone. We can have everything: ownership, privacy, performance, and ease of use.
02

Verify, Don't Compute

Blockchains are for verification, not computation. Trying to make a blockchain into a "world computer" was the first fundamental error. Web5 holds that consensus and final settlement happen on-chain. Everything else, computation, storage, application logic, happens off-chain where it belongs.

This is the architectural principle behind CKB's design: the chain verifies state transitions, it doesn't execute them. Scripts running in CKB-VM validate that a transaction's outputs comply with defined rules, but the actual computation that produced those outputs happens off-chain.
03

True Digital Ownership

In the account model, all assets except the native token are custodied by smart contracts. The contract owner can mint, burn, or confiscate tokens. In CKB's Cell model, every asset is a first-class citizen directly controlled by the user's private key. Even if a token contract is compromised, the attacker cannot touch your assets.

Token contracts in CKB define rules (e.g., "total supply capped at 1 million"). But the actual asset records live in cells owned by users. The contract validates behavior; it does not custody assets. This is the difference between a law and a vault.
04

Privacy as Infrastructure

Off-chain verification naturally preserves privacy. Your asset state and transaction history are not broadcast to the world. This is not an added feature or an opt-in layer. It is a structural property of the architecture, like cash being more private than wire transfers by design.

Fiber Network extends this principle to payments. Transactions within Fiber channels are private between the two parties involved. Only channel open and close operations touch the public chain. The bulk of economic activity happens off-chain, invisible to surveillance, as it should be.
05

AI Agents Are Native Citizens

In Web5, AI agents are not tools bolted onto an existing system. They are first-class participants alongside humans. Agents run nodes, manage keys, handle configuration, build indexes, execute transactions, and interact with the network on equal footing. The UTXO model and CKB-VM make no distinction between a script triggered by a human and one triggered by an agent.

Web 2.0 centralized services won because they required zero client-side setup. The tradeoff was giving up ownership, privacy, and performance. With agents as native citizens of the network, that tradeoff dissolves. Agents handle the complexity that kept local-first impractical: node setup, key management, data indexing, protocol negotiation. Humans retain ownership and sovereignty. Agents provide the operational layer. Fiber Network is especially powerful here: agents can open payment channels, execute micropayments, and settle cross-chain swaps autonomously, enabling machine-to-machine economies that run without human intervention.
06

Open and Interoperable

Web5 is not one chain or one protocol. It is a mesh of PoW+UTXO consensus layers, channel networks, and open protocols. Bitcoin, CKB, Nostr, and systems not yet imagined can interoperate within this mesh, each contributing its strengths to a network no single entity controls. CKB's blockchain abstraction design makes this concrete: by not hardcoding any cryptographic primitive into the VM, CKB can verify signatures and proofs from any blockchain natively. Applications built on CKB are not locked to one chain's assumptions.

// technology

The Stack

The building blocks of Web5.

Architecture Layers

APPLICATIONS DApps · DeFi · Social · Identity · NFTs PROTOCOLS RGB++ · Fiber Network · Open Social Protocols L1 — PoW + UTXO CONSENSUS Bitcoin · CKB (Cell Model + RISC-V VM) Bitcoin anchors consensus. CKB extends programmability. Both are PoW+UTXO.
  • L1

    Bitcoin, CKB

    PoW + UTXO Consensus Layers

    Bitcoin provides the ultimate settlement layer and security anchor. CKB extends the PoW+UTXO paradigm with full programmability: a universal verification machine built on the Cell model and RISC-V VM. Together they form the L1 foundation of Web5. CKB is the public bulletin board, the shared source of truth that local-first nodes read from and write to. Bitcoin is the consensus anchor that everything ultimately settles against.

    Through RGB++, Bitcoin gains programmability without modifying its own protocol. Bitcoin UTXOs serve as binding points for CKB Cells. CKB uses a state-rent model where occupying on-chain storage requires locking CKBytes. Primary issuance follows Bitcoin's halving curve. The Cell model generalizes UTXOs into universal containers for arbitrary data, scripts, and state. CKB-VM runs on the open RISC-V instruction set, supporting scripts in C, Rust, or any language that compiles to RISC-V. Cryptographic primitives are not hardcoded, they are scripts, making CKB maximally flexible and future-compatible.

  • L2

    Fiber Network

    CKB Lightning Network

    A next-generation public lightning network built on CKB and off-chain channels. Fast, low-cost, decentralized multi-asset payments and P2P transactions. Natively supports cross-chain atomic swaps with Bitcoin's Lightning Network.

    Fiber uses the same hash algorithms and timelock scripts as Bitcoin Lightning, enabling natural interoperability. It supports RGB++ assets and Taproot assets. Channel open/close fees on CKB are substantially lower than on Bitcoin mainnet.

  • PROTOCOL

    RGB++

    Isomorphic Binding

    RGB++ creates a binding between Bitcoin UTXOs and CKB Cells through isomorphic mapping. No cross-chain bridge needed. Bitcoin gains Turing-complete contract capabilities through CKB, with trustless verification.

    RGB++ transforms RGB's off-chain client-side validation into CKB's on-chain public verification. Bitcoin UTXOs serve as RGB containers that map to CKB Cells. Through this binding, CKB Cells inherit control from Bitcoin addresses.

  • SOCIAL

    Open Social Protocols

    Decentralized Identity and Communication

    Web5 embraces open social protocols as the identity and communication layer. Nostr provides censorship-resistant messaging with cryptographic identity. AT Protocol (Bluesky) offers federated social networking with portable accounts. Both can bind to CKB Cells, connecting social identity to digital ownership. The did:ckb method anchors decentralized identifiers directly on CKB, giving every identity on-chain verifiability and self-sovereignty.

    The Nostr Binding Protocol establishes a 1:1 mapping between Nostr Events and CKB Cells, making every Nostr account a CKB wallet. AT Protocol's DID-based identity model aligns with Web5's self-sovereign principles. did:ckb takes this further: it is a W3C-compatible DID method where identifiers are resolved and verified through CKB on-chain state, requiring no centralized registry. These protocols provide the social substrate: data definition and communication happen in the social layer, ownership and identity guarantees come from the blockchain layer.

  • APP

    Local-First Software

    Your Stack, Your Machine

    The top of the Web5 stack is where you live. Local-first software runs on your machine, stores data on your disk, and serves you directly. Not a client connecting to someone else's server. A full application stack you own and operate: CKB node, Fiber node, indexer, explorer, wallet, and whatever else you choose to run. If the network goes down, your software still works. When it comes back, it syncs.

    Local-first software is not new. What is new is connecting isolated local-first programs into a network through CKB's trustless P2P consensus. Each node is self-sufficient: it reads from its own CKB node, builds its own indexes, serves its own UI. No RPC provider dependency. No API rate limits. No terms of service. The chain is the single source of truth. Everything else is derived locally. If the database breaks, rebuild it from the node. As long as you have a CKB node, you can always rebuild.

Ownership: Account Model vs Cell Model

ACCOUNT MODEL User (EOA) Contract (custodian) Assets CELL MODEL User (private key) direct Assets (in Cells) No intermediary. No custodian.

The Local-First Network

EACH NODE RUNS ITS OWN STACK NODE A your apps fiber node indexer / explorer CKB node runs locally NODE B your apps fiber node indexer / explorer CKB node runs locally NODE C your apps fiber node indexer / explorer CKB node runs locally CKB L1 — PUBLIC BULLETIN BOARD shared state · consensus · verification P2P network CKB nodes connect the stacks. The P2P network is the messaging protocol. L1 is the bulletin board.
// explore

Resources

Go deeper. Join the movement.

Core Reading

Protocols

Ecosystem

Build