| Author | Jan Xie |
|---|---|
| RFC created | January 2, 2018 |
| Category / status | Informational / Final |
| Project | Nervos CKB |
| License | No license is listed in the RFC metadata. |
| Official document | RFC-0002: Nervos CKB: A Common Knowledge Base for Crypto-Economy |
This page is an educational summary and analysis of the linked technical paper, not a reproduction. CryptoGloss does not claim authorship of the original work; rights remain with the author or applicable rights holders.
In brief: RFC-0002 presents Nervos CKB as the base verification and state layer of a multi-layer crypto-economy. Its Cell model borrows the consume-and-create pattern of Bitcoin UTXOs but adds general state data and separate validation scripts. The document is a design overview, so it should not be read as a description of every later CKB upgrade or application.
What RFC-0002 describes
The official RFC metadata names Jan Xie as author, marks the document Informational and Final, and records its creation date as January 2, 2018. The paper introduces the Nervos Common Knowledge Base (CKB), a public, permissionless Layer 1 intended to hold state that can be checked through network-wide consensus. The RFC describes a proposal and its design rationale; later implementation details and economic refinements are documented separately in other RFCs and current developer documentation.
A layered network design
RFC-0002 divides the proposed network into two broad roles. CKB is the verification layer: it stores state and provides a shared trust root. Layer 2 systems generate state changes and can handle higher-throughput transactions or privacy features, then submit relevant results to CKB for verification when needed. This is the architecture described by the paper, not a claim that every present-day Layer 2 uses the same design or security model. The distinction is set out in the RFC-0002 overview and the current Nervos blockchain guide.
The Cell model
A Cell is CKB’s basic on-chain unit for holding state. The model is inspired by Bitcoin’s UTXO approach, where transactions consume existing outputs and create new ones. CKB generalizes that pattern: a Cell can contain arbitrary data and uses scripts to separate ownership checks from rules about valid state transitions. It is therefore related to a UTXO, but it is not simply an identical Bitcoin output, and the two systems should not be assumed to have identical security properties.
| Cell field | Role |
|---|---|
capacity |
The CKByte capacity assigned to the Cell; it must cover the size of the Cell’s serialized contents. |
data |
The state bytes stored by the Cell. |
lock |
A required script that controls who can consume or transfer the Cell. |
type |
An optional script that checks rules for the Cell’s data or its use in a transaction. |
Cells are immutable once created. To update state, a transaction consumes a live Cell and creates a replacement with new data; the old Cell becomes historical rather than being edited in place. Lock scripts check permission to spend, while type scripts validate application-specific conditions. The official Cell Model guide and Cell structure reference explain the lifecycle and fields. A comparison with Bitcoin’s UTXO model is available in the CKB vs. BTC guide.
CKB-VM and scripts
CKB-VM executes the lock and type scripts that validate Cell transactions. RFC-0003 specifies a virtual machine based on the RISC-V instruction set; its design uses standard RISC-V instructions rather than treating every cryptographic operation as a special protocol opcode. This lets developers build scripts with toolchains that target the supported RISC-V environment, subject to CKB’s execution and transaction rules. The separate RFC-0003 CKB-VM specification is the technical source for those details.
Proof of work and current consensus
The Nervos network uses proof of work. Current Nervos documentation describes NC-Max as its consensus algorithm and Eaglesong as the mining hash function. Those are related but different parts of the system: consensus defines how the network selects and accepts blocks, while the hash function is used in the proof-of-work process. The original RFC-0002 is a high-level architecture paper, so current consensus details should be checked against the maintained blockchain documentation and mining guide.
CKByte capacity and storage economics
CKB is the network’s native token and also represents capacity for occupying on-chain state. In the protocol’s accounting model, one CKB corresponds to one byte of capacity, but a Cell’s capacity must cover its serialized contents, including its data and structure; it is not a promise that every token buys one byte of application data with no overhead. CKB is also used for transaction fees. When a Cell is consumed, its capacity can be reassigned in the resulting transaction.
The economic design is more nuanced than “storage without rent.” RFC-0015 describes secondary issuance as a way to price long-lived state use over time. CKB used to occupy state can be exposed to dilution from that issuance; the NervosDAO is designed to return a share of secondary issuance to eligible deposits that are not using capacity for state storage. The exact distribution depends on the network’s usage and issuance rules. This is not a periodic rent bill, but it also does not mean storage has no economic cost. See RFC-0015 on CKB cryptoeconomics and the maintained CKB rewards documentation.
Issuance: base and secondary rewards
CKB has more than one issuance stream, so a single “fixed supply” description would be incomplete. Current Nervos documentation lists a total of 33.6 billion CKB from base issuance, distributed on a schedule that halves roughly every four years. Separately, the protocol issues a fixed amount of secondary issuance each year; its allocation changes with network use, with portions going to miners and the NervosDAO and an unallocated portion subject to the protocol’s treasury or burn rules. Transaction fees are another source of miner rewards. The official halving schedule covers base issuance only, while the rewards guide explains the different components. These mechanics are protocol descriptions, not a forecast of CKB’s price or return.
Later development: RGB++
RGB++ is a later protocol associated with Nervos, not a section of the 2018 RFC-0002 proposal. Current Nervos documentation says it maps Bitcoin UTXOs to CKB Cells through isomorphic bindings and uses scripts on both networks to validate related state and ownership changes. That relationship can connect the two state models, but it does not make the original CKB paper a specification for RGB++. Read the maintained RGB++ protocol documentation for its own scope and mechanisms.
How to read the paper today
RFC-0002 is useful for understanding the motivation behind a layered Nervos network, the Cell model, and CKB’s state-verification role. It should be read alongside later specifications for CKB-VM and cryptoeconomics, plus current developer documentation for the implemented network. The paper does not by itself establish current adoption, performance, market value, or the security assumptions of every application built on CKB.
Related Terms
- UTXO — the unspent-output model that inspired the Cell design.
- Proof of Work — the consensus family used by the Nervos network.
- Layer 1 — CKB’s role as the network’s base verification layer.
Related Articles
- Are Layer 2 Networks Actually Decentralized? — examines the security and decentralization assumptions of layered blockchain designs.
- Does Ethereum TPS Include Layer 2 Transactions? — explains how Layer 1 and Layer 2 activity are counted.
- What Do Zero-Knowledge Proofs Actually Guarantee in Blockchain? — clarifies what a cryptographic proof can and cannot establish.
See Also
- Bitcoin: A Peer-to-Peer Electronic Cash System — the design paper behind the UTXO-inspired comparison.
- Ethereum: A Next-Generation Smart Contract and Decentralized Application Platform — a contrasting account-based smart-contract design.
- Polkadot: Vision for a Heterogeneous Multi-Chain Framework — another proposal for a layered, multi-chain network.
Sources & Further Reading
- Jan Xie, RFC-0002: Nervos CKB: A Common Knowledge Base for Crypto-Economy — primary source for the paper’s date, status, layered architecture, Cell model, and original design goals.
- Nervos CKB Docs, Cell Model — explains Cell immutability, consumption, replacement, and script validation.
- Nervos CKB Docs, Cell Structure — defines capacity, data, lock, and type fields.
- Nervos CKB Docs, CKB vs. BTC — compares Bitcoin UTXOs with CKB Cells and their scripts.
- Xuejie Xiao, RFC-0003: CKB-VM — specifies the RISC-V-based virtual machine used to execute CKB scripts.
- Nervos RFCs, RFC-0015: CKB Cryptoeconomics — describes base and secondary issuance, state-rent design, and the NervosDAO role.
- Nervos CKB Docs, Nervos Blockchain — summarizes the current layered network, Layer 1 role, CKByte capacity, and NC-Max consensus.
- Nervos CKB Docs, Mining Rewards — details current base, secondary, proposal, and commitment rewards.
- Nervos CKB Docs, Halving — gives the base-issuance total and halving schedule.
- Nervos CKB Docs, RGB++ Protocol — describes the later protocol’s mapping between Bitcoin UTXOs and CKB Cells.