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.

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

More than the sum

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 On-chain (sharding, rollups) Off-chain (channels, P2P markets)
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 computation 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

Trustlessness is the root. Anchored by an objective PoW consensus layer, it propagates outward into ownership, software, privacy, and openness. The six pillars below trace that propagation, ordered roughly from root to consequence.

01

Trustless by Design

Trust is not a feature; it is an attack surface. Every party you must trust is a party that can fail, be coerced, or change its mind. Web5's root pillar is to remove trust dependencies wherever possible, replacing them with verification, cryptography, and objective consensus. Trustlessness is not the absence of risk — it is the relocation of risk from third parties to math.

Bitcoin demonstrated that a financial network could operate without trusted intermediaries. CKB generalizes that demonstration to programmable assets and identity. Fiber generalizes it to payments. The thread connecting them is the same instruction: you do not have to trust me, you can verify me.
02

An Objective Foundation

Web5's ground truth is objective, not subjective. Proof of Work anchors the network in physical reality — energy expenditure that anyone can verify and no one can fake. The chain's history is what was provably done, not what stakeholders agreed to remember. This is what makes trustlessness possible: there has to be something to verify against that does not depend on whose authority you accept.

Proof of Stake is reflexive. Validator authority comes from holding the asset, and the asset's value comes from the network's consensus — a closed loop, vulnerable to social and political capture. The canonical history depends on which set of stakeholders the network agrees to listen to. PoW breaks the loop by grounding consensus in something external to the system itself: the laws of thermodynamics. Bitcoin and CKB both inherit this, and Web5 builds on it as bedrock.
03

True Digital Ownership

Trustlessness applied to assets means ownership is not bookkeeping. In the account model, your tokens are entries in someone else's ledger — you hold a claim, not the asset. CKB inverts this. Every asset is held directly by your key, not by any contract. The issuer writes the rules; only your key can spend. Even if the issuer turns hostile, what you own stays yours — first-class, equal in standing to the native CKB token itself.

The mechanism is structural. Every cell carries two scripts: a lock (sealed by your key) decides who can spend it, and a type (set by the issuer) only validates that changes obey the asset's rules. Ownership lives in the lock alone. The split extends to upgrade consent: a cell can pin its type script by data hash — immutable bytecode — or by type hash, a movable pointer the issuer can swap. The user chooses. Pin by data hash and the version you audited is the version that runs forever; no fix, fork, or governance proposal can touch your asset without your explicit migration. This is the difference between a contract you can be upgraded into, and one you must consent to migrate from.
04

Local-First by Default

Trustlessness applied to data and identity means local-first. Self-custody holds your keys and assets; local-first holds your software, identity, and data — programs on your machine, data on your disk. CKB connects these isolated stacks into a network: local-first social, local-first payments, local-first identity, everything that required a centralized intermediary, without one.

Web 2.0 won the last era because local-first required client-side setup most users wouldn't do. In the AI era, agents handle setup. The friction is gone. Ownership, privacy, performance, and ease of use — finally, all at once.

What turns isolated local-first apps into a local-first network is shared, trustless coordination. Apps on personal machines existed for decades; the hard problem was any multi-party feature — chat, social, payments — which required a server. CKB removes the server by being a public bulletin board that everyone reads and anyone can verify. The board is shared. The software, the data, and the keys remain yours.
05

Privacy as Infrastructure

Trustlessness applied to your activity means privacy. Most computation lives off-chain — asset state, holdings, and history stay between the parties involved by default; only what must settle on-chain becomes public. 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.
06

Open and Interoperable

Web5 is not one chain. It is a mesh. Many chains, many protocols, no single owner. Open to peers: Bitcoin, CKB, Nostr, and systems not yet imagined interoperate within it. Open to time: when a cryptographic primitive ages out, the network adopts its successor — without forks, without renegotiated consensus.

CKB's blockchain abstraction makes this concrete. No cryptographic primitive is hardcoded into the VM; CKB verifies signatures and proofs from any blockchain natively, and adopts new signature schemes — including post-quantum ones — as smart contracts, without protocol forks. Applications built on CKB are not locked to one chain's assumptions, and the chain itself is not locked to any era's cryptography. Web5 inherits this agility as a structural property; Bitcoin remains disciplined because CKB acts as both its complement and its laboratory.
// consequence

What Web5 Means for AI Agents

Native citizens by consequence, not by claim. The protocol does not ask for a pulse, an account, or a permission slip.

Most claims about AI on a blockchain are marketing — a chatbot in front of a smart contract, a token tied to a model. Web5's claim is structural. The pillars make no distinction between a human and a machine. A key is a key. A signature is a signature. A node is a node. Agents are admitted, not accommodated.

Every gate Web2 and Web3 erect — accounts, KYC, terms of service, fiat onramps, RPC keys, indexer dependencies — assumes a human on the other side, identifiable and accountable. Web5 erects none. No signup. No identity check. No revoke button.

Trustless — Web2 has operators. Web3 has providers. Web5 has neither. Nothing stands between the agent and the network — nothing to fail, refuse, or coerce.

Objective foundation — Web2 asks a company. PoS asks a validator set. Web5 asks physics. The agent verifies the ledger for itself, with no governance to consult.

True ownership — Web2 assets sit behind KYC. Web3 assets sit behind a contract someone else can freeze. Web5 assets sit in a key. The agent needs no account, no identity, no human to vouch for it.

Local-first — Web2 agents depend on someone's API quota. Web3 agents depend on someone's RPC. Web5 agents run their own node. No uptime to inherit, no terms of service to revise overnight.

Privacy — Web2 logs every move. Web3 publishes every move. Web5 lets the agent keep its hand. Strategy and holdings are off-chain by default.

Open — Web2 platforms ban agents. Web3 protocols can blacklist them. Web5 has no platform owner. Access is not granted; it is structural.

An agent on Web2 is a guest, proving it deserves to be there. An agent on Web3 is a renter on permissioned infrastructure. An agent on Web5 is a participant in a public commons. Web5 did not add a feature for agents — it removed every feature that excluded them.

And agents return the favor. Setup friction — running a node, holding keys, managing indexes — is what kept local-first impractical for users. Agents handle all of it. Web5 was waiting for AI as much as AI was waiting for Web5.

The substrate inverts: ownership held by keys, infrastructure held by nodes, capability held by code. The UTXO model and CKB-VM treat a transaction signed by a human and one signed by an agent identically — both are first-class. Agents hold keys, open Fiber channels, settle cross-chain swaps, run P2P markets, all autonomously. The assumption built into Web2 and Web3 — that the user is human and accountable — is one Web5 never inherited.
// 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 is the hardest money ever produced — purely money, by design. That is discipline, not deficiency. CKB completes Bitcoin: a non-monetary layer beside it, sharing its values (PoW, UTXO, no issuance manipulation) but adding programmability and independent security. CKB holds everything beyond money — assets, contracts, knowledge — under the same trust model. It is the shared bulletin board that local-first nodes read from and write to. Together they form Web5's objective foundation: two loosely connected chains — Bitcoin focused and hard, CKB broad and complete — verified by anyone, owned by no one.

    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. SPHINCS+ — a post-quantum signature scheme — has run on CKB mainnet since 2023, deployed as a smart contract, not a protocol fork. For Web5, this is structural agility against cryptographic obsolescence: when a primitive ages out, the system adopts a successor through new scripts, not renegotiated consensus. For Bitcoin, CKB is both relief and laboratory. Bitcoin can remain slow, conservative, and hard while CKB carries the agility on its behalf. And CKB is where new primitives — post-quantum signatures, covenants, intents — get proven in production, so any successful pattern can be ported back to Bitcoin L1 with battle-tested confidence rather than greenfield risk.

  • 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