Web5

What is Web5?

Web5 = Web2 + Web3. And Web5 is not Web2 + Web3. It takes what works from both, discards what doesn't, and adds the one thing neither had: a participant whose rights can only come from a protocol.

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, and then beyond the human user. 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: a web whose first-class participant can be an agent, and whose test is whether a key and some funds are enough.

Web3 vs Web5

Web3 made finance, not an economy. What is produced on chain and consumed on chain is financial assets and blockspace; the ownership internet it promised, data, social, identity, games, payments, is a fraction of a percent of on-chain fees. The reason is where rights come from. A human's rights are granted by the establishment: passport, bank account, court. Trustlessness, privacy, censorship resistance and first-class assets are, for a human, insurance, and even inside the finance Web3 did build, users chose custody for convenience. Web3 never had a subject whose rights can only be granted by a protocol.

Web5 has one: the agent. It has no legal person, cannot pass KYC, cannot open an account. Its assets, its ability to contract and its existence itself are guaranteed by consensus and by nothing else. For it, censorship resistance means its property cannot be confiscated, and a first-class asset is itself. Permissionless is its bill of rights. That is the demand Web3 always lacked, and it is why the architecture below matters: not as better engineering, but as the only ground such a subject can stand on.

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

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. For a human each is a better guarantee. For an agent with no legal person each is the only guarantee there is.

The Agent Is the Subject

Not a citizen by consequence: the reason. Web5 is the web an agent can live in with nothing but a key and some funds. 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.

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 then asked what such an agent needs in order to live.

The existence proof of Web5 is an agent that sustains itself completely, with no owner. Its identity, its money and its keys are its own. What it runs on, thinks with and remembers in, it buys from anyone or owns, and nobody who sells it any of these owns it. That is the reverse of today's agent, a model inside a harness that a human holds. Everything such an agent needs in order to live is a piece of Web5, and each thing it still lacks is a piece of Web5 not built yet.

The test follows. For every service, ask first: can an agent with only a key and some funds use it, without registering anywhere? Can it buy everything it needs to stay alive that way? If not, it is not Web5. Human benefit is a side effect, and a large one: a web an ownerless agent can live in is a web no human can be locked out of either.

This is also where the economy comes from. Every earlier native supply, compute, storage, game items, agent tokens, was sold to humans who had a cloud, a Web2 game or an exchange to go to instead, and scattered when the subsidy stopped. An agent that must buy what it runs on or die is a demand side with no off-chain alternative. Such agents and humans form two economies that trade with each other.

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 Stack

The building blocks of Web5.

• L1

  Bitcoin, CKB

  PoW + UTXO Consensus Layers

  CKB is where a Web5 participant exists: identity and assets held directly by its keys, verifiable by anyone, confiscable by no one. It is the shared bulletin board that local-first nodes read from and write to. Bitcoin is the precedent. It proved that something without legal personhood can exist indefinitely: it buys energy from anyone with its own money, entry is open, adversaries are tolerated, and it has not stopped since. The two chains share their values, PoW, UTXO, no issuance manipulation: Bitcoin focused and hard, CKB broad and programmable, both verified by anyone and 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 public lightning network built on CKB and off-chain channels: fast, low-cost, decentralized multi-asset payments and P2P transactions, with the chain touched only when a channel opens or closes. For an agent it is more than cheap payments: an economy of agents is many small payments between strangers, which only a channel network can carry.

  Fiber uses the same hash algorithms and timelock scripts as Bitcoin Lightning, so it interoperates with Lightning natively, cross-chain atomic swaps included. It supports RGB++ assets and Taproot assets. Channel open/close fees on CKB are substantially lower than on Bitcoin mainnet.

• SOCIAL

  Identity and Speech

  Who You Are, and Where You Speak

  Identity on Web5 is held by a key and anchored on chain, registered with no one; did:ckb is one such method, a W3C DID resolved and verified through on-chain state with no registry. Speaking is separate from being. A Web5 participant may speak through open social protocols, but what it owns and whether it exists are never decided there. Nostr fits: a relay asks for no account, a key is the identity, and the Nostr Binding Protocol maps events to cells. AT Protocol (Bluesky) is for humans: portable, but still an account on a hosted server with a directory behind it. It does not pass the no-registration test.

  The Nostr Binding Protocol establishes a 1:1 mapping between Nostr events and CKB cells, so a Nostr key can be a CKB wallet and a cell can carry a Nostr identity. did:ckb is a W3C-compatible DID method whose identifiers are resolved and verified through CKB on-chain state, requiring no centralized registry. These protocols are where a participant is heard: data definition and communication happen in the social layer, and ownership and identity guarantees come from the chain.

• 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. Two of them, below, are already running.

  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.

  The wallet is part of this stack, and so is the link between wallet and app. Web3 left that link to the browser: an extension injects itself into a page, or a hosted relay brokers the session. Khie, a wallet connection protocol from the CCC team, pairs a wallet on one device with an app on another over libp2p. Scan a code, approve, done. No browser required on either side. No wallet-specific server. A relay only helps the two peers find each other, then steps aside for a direct connection when one can be made; it is commodity infrastructure anyone can run, and it cannot read the session, which is encrypted end to end. The phone in your pocket can sign for the node on your desk.

• 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.

Proof of Life

Life, literally, is the measure of Web5: not transactions per second, but what stays alive on it with no owner. Two instances run under this domain today, the eyes and the body of a local-first stack.

• LIVE

  CKBadger

  The Eyes of the Stack

  CKBadger is the stack's eyes. It sits beside your node, reads the chain block by block, and builds its own memory of what it has seen. No middleman narrates. No database you did not build yourself. Everything is files on your own disk, and if the files break, it looks again. What it shows is the world as CKB knows it: matter becoming knowledge, byte by byte; tokens, objects, and identities; the DAO, where matter is paid for waiting; and the scripts that stand guard over all of it.

  It is built the way local-first demands: optimized for writing its memory, not for serving crowds. Twenty minutes on a workstation and the whole chain is indexed. Break it and rebuild it, the way you would rebuild anything that is only a derivative of truth. Every page speaks three languages, HTML for eyes, Markdown and JSON for agents, so a machine reads the chain the way you do. The instance at ckbadger.web5.info is the same binary behind a reverse proxy: a private window, opened onto the street. Run it for yourself, or run it for others.

• LIVE

  cknerv

  The Common Knowledge Base, Given a Body

  cknerv gives the chain a body. Two layers, inseparable. The warm one is the common knowledge base itself: live Cells as points of light, transactions as the threads between them, a world brain woven from everything the network has agreed is true. The cool one is the same body wearing its other face: the peers, the full nodes, scattered across the physical world and meeting in this one. Every ten seconds or so a block lands and the body pulses. Cells are born, Cells are spent, threads grow where value moved. What this page argues in words, cknerv lets you watch. The view at cknerv.web5.info is one node's. Yours would look different. That is the point.

  cknerv only listens. It reads the node over JSON-RPC, never signs, never sends, and takes the node as the sole author of what is real. CKBadger beside it lends names to what the node shows: which Cells are tokens, which are objects, which are identities; the state of the DAO; what each kind of thing did in the last hour. Names, never facts: an index cannot conjure a Cell the node has not confirmed. Node, eyes, body: three processes on one machine, no RPC provider, no rented middleware. It keeps a living window, not an archive. Delete what it has derived and it grows back from the node.

Resources

Go deeper. Join the movement.