Nervos Network (CKB)

Overview

Common Knowledge Base is the foundational blockchain of the Nervos Network. It uses proof-of-work consensus and represents state as live cells that transactions consume and recreate, allowing flexible ownership and type scripts. CKB-VM executes RISC-V based scripts, while one CKB represents a unit of on-chain state capacity. The model differs from both account balances and Bitcoin’s simple UTXO use. Transaction cycles, cell dependencies, witnesses, and occupied capacity affect validity and fees.

Wallets and payment services should validate the CKB network, address format, cell structure, capacity, fee, and confirmations. Developers must preserve required cell data and dependencies when constructing transactions. Token standards on CKB have separate identifiers and should not be confused with the native capacity asset. This prevents later renames, forks, or infrastructure changes from making previous settlement decisions impossible to reproduce. Historical records involving Nervos Network (CKB) should retain chain identifiers, block hashes, transaction data, and the configuration version used at acceptance time.

Nervos Network (CKB) should be identified by its active mainnet, chain or network identifiers, native fee asset, address rules, and currently supported software. A project name, associated token, testnet, legacy deployment, and bridged representation are different objects and should not be used interchangeably.

Public endpoints and explorers are useful operational tools but are not independent proof that a node is synchronized or a transaction is canonical. Integration with Nervos Network (CKB) should use current official specifications for RPC methods, transaction formats, fees, finality, contract addresses, and upgrade schedules. Practical implication: Nervos CKB combines proof of work with programmable state cells, requiring cell-capacity, script, dependency, fee, and confirmation awareness.