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.
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.
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.
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.
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.
Most of what follows in this list is the same principle applied to a different layer. Non-custodial ownership refuses to trust contract owners with your assets. Local-first refuses to trust servers with your data and identity. Privacy refuses to trust the network with your transaction history. Trustlessness is not the absence of risk — it is the relocation of risk from third parties to math.
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.
True Digital Ownership
Trustlessness applied to assets means non-custodial. 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.
Local-First by Default
Local-first extends self-custody. Self-custody holds your own keys and assets; local-first holds your identity and data too — software running on your machine, storing data on your disk, serving you directly.
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 connect isolated local-first programs 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.
Privacy as Infrastructure
Off-chain computation 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.
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.
What Web5 Means for AI Agents
Native citizens by consequence, not by claim. The same pillars that protect humans give agents the same powers — the network does not check who is asking.
Most claims about AI on a blockchain are marketing. Web5's claim is structural: the pillars that define this network do not distinguish between human and machine participants, so agents become first-class actors as a consequence — not as a separate feature bolted on for the press release.
A human and an agent both need the same things from a network: the ability to act without permission, hold assets without intermediaries, run software without vendor dependency, and be verified without revealing private state. The pillars provide those things. They do not ask whether the signer of a transaction has a pulse.
Trustless — an agent does not need to trust a service operator to act on the network, because there is no operator in the loop.
Objective foundation — an agent has a deterministic source of truth it can verify and replay independently, with no dependency on which validator set is currently in favor.
True ownership — an agent that controls a key controls real assets, not access to a contract that custodies them on its behalf.
Local-first — an agent runs its own node and holds its own state. Its capabilities are not at the mercy of a vendor's uptime, terms of service, or rate limits.
Privacy — an agent's strategy, holdings, and history are not broadcast to the world by default.
Open — no platform owner can revoke an agent's access, because there is no platform owner.
The UTXO model and CKB-VM make no semantic distinction between a transaction signed by a human and one signed by an agent. Both are first-class. Both have the same powers. This is why machine-to-machine economies become tractable on Web5: agents can hold keys, open Fiber payment channels, settle cross-chain swaps, participate in P2P markets, and do all of this autonomously, without humans-in-the-loop and without permission gates.
The Stack
The building blocks of Web5.
Architecture Layers
-
L1
Bitcoin, CKB
PoW + UTXO Consensus LayersBitcoin 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 NetworkA 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 BindingRGB++ 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 CommunicationWeb5 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 MachineThe 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
The Local-First Network
Resources
Go deeper. Join the movement.