The Cell Model is Nervos CKB’s generalized UTXO-style state model. Instead of changing a balance record in place, a CKB transaction consumes existing Cells and creates new ones; each Cell can carry capacity and data governed by scripts. [1]
| Protocol documentation | Open documentation |
|---|---|
| Directories | Nervos Ecosystem Directory |
How Cells represent state
A Cell is an on-chain output that remains immutable after creation. It can hold CKB capacity, data, or both. When an application changes a value stored in a Cell, the transaction spends that live Cell and creates a replacement output with the updated state. A consumed Cell is no longer available to spend again, which is the core UTXO-like property. [1][2]
This model gives CKB a common way to represent assets and application state. Tokens, collectibles, and other data-bearing outputs can all be represented through Cells, while their meaning comes from the rules attached to them. The comparison with Bitcoin’s UTXO model is useful, but CKB Cells can also carry application data and participate in richer script rules. [1]
Scripts decide what a transaction may do
A Cell’s Lock Script sets the conditions for consuming it. A Type Script can enforce rules about a Cell’s data or about how a transaction transforms that data. During validation, CKB executes the scripts associated with a transaction’s inputs and outputs; if their conditions fail, the transaction is invalid. [1]
For developers, this shifts some design work toward the structure of Cells and the scripts that validate transitions. Applications must define which Cells may be combined, what data is carried forward, and which checks apply when state moves. CKB-VM is the execution environment for these scripts, while the Cell Model describes the state and transaction structure they operate on.
Capacity makes storage visible
CKB capacity is tied to the space a Cell occupies. Storing more data therefore has an on-chain resource cost: the Cell must hold enough capacity for its serialized contents, and its owner is responsible for the storage associated with it. Official CKB documentation describes a minimum of 61 CKBytes for a standard empty Cell and recommends extra capacity for fees; exact requirements depend on the Cell’s data and scripts. [2]
The trade-off is explicit storage and flexible state representation, paired with the need to plan capacity and manage spent and newly created outputs. That is a design consequence of the model, not a promise of cheaper transactions or automatic scalability. The practical cost still depends on transaction contents, network conditions, and application design.
A useful comparison
Think of a Cell like a sealed container whose contents are not edited on-chain: a valid transaction consumes it and creates a new container. This is different from the familiar account model, where a contract commonly updates a value associated with an account. The distinction affects how developers model state and how wallets assemble transactions; it does not by itself determine whether an application is secure or easy to use.
See Also
Sources
Last updated: November 4, 2026.