CKB-VM

CKB-VM is the virtual machine used to execute scripts during Nervos CKB transaction validation. It is built around the RISC-V instruction set, so the machine architecture differs from Ethereum’s EVM and does not mean EVM bytecode or Solidity contracts run on CKB unchanged. [1][2]

Protocol documentation Open documentation
Directories Nervos Ecosystem Directory

What it executes

CKB uses scripts to apply spending and data-validation rules to Cells. CKB-VM provides the environment in which those scripts run when nodes verify a transaction. In the CKB model, the virtual machine and the Cell state model work together: Cells carry state, while scripts define conditions for consuming or creating them. [1]

This is why CKB-VM is not a separate blockchain or a generic account database. It is a protocol component invoked to check whether a proposed state transition obeys the relevant scripts. The final validity of a transaction depends on those rules and the chain’s consensus, not merely on code executing successfully in an application’s own interface.

RISC-V and developer choice

RISC-V is an instruction-set architecture. Nervos documentation says languages that can target RISC-V can be used for CKB script development and lists native SDKs for languages including JavaScript, Rust, Go, Java, and Ruby. [1] RFC #0003 gives the lower-level specification and describes how the VM checks transaction inputs and outputs. [2]

That flexibility is about the target architecture, not a guarantee that every language has equally mature libraries, tutorials, auditing tools, or production deployments. Developers still need CKB-aware code, serialization, testing, and deployment tooling. The language name alone does not make a contract compatible with CKB-VM.

How it differs from the EVM

Ethereum’s EVM is associated with Ethereum’s account and contract execution model. CKB-VM runs RISC-V-based scripts within CKB’s Cell and transaction model. A developer can build familiar application behavior on CKB, but typically must compile or implement it for the CKB environment and follow its script and Cell rules; copying an EVM contract bytecode file is not enough. This is a useful distinction for developers comparing chains, wallets, and application support.

What to check before building

A project should confirm its chosen language toolchain targets the supported RISC-V environment, inspect the relevant CKB SDK and Script APIs, and test transaction validation against current node versions. The VM evolves through versioned protocol changes, so the current documentation and RFCs are more reliable than assumptions based on a generic RISC-V or EVM description. [1][2]

See Also

Sources

  1. [1] Nervos CKB, CKB-VM documentation
  2. [2] Nervos RFC #0003: CKB-VM

Last updated: November 4, 2026.