CKB Dev Log 2026-10-14

[chenyukang]

Updates

This cycle (September 16–October 13, 2026) brought the CKB v0.210.0 release, further node and networking hardening, and improvements to local development tools. DAO treasury research moved from the previous issue’s voting specification into an experimental implementation with SDK support.

Key milestones include:

• CKB v0.210.0 shipped, including earlier validation of header requests and DAO transactions.
• CKB-VM and Tentacle landed runtime and networking improvements, while ckb-cli integrated its terminal interface.
• Light-client verification advanced through new and revised proposals that remain open.
• DAO voting gained an experimental implementation, with further changes to vote thresholds and proposal settlement.

Releases & Features

CKB v0.210.0

CKB v0.210.0 was released on September 17. This regular minor release carries forward the previous cycle’s node hardening and CKB-VM v0.24.15 update. It also contains some security patches such as checks header-request locator lengths before allocating entries and validates DAO lock size before transaction-pool script execution, rejecting malformed input before unnecessary processing.

faster-hex 1.0

The faster-hex v1.0.0 release, published September 23, introduces a checked API that decodes the complete input, returns the written output slice, and preserves destination buffers on checked errors. It removes public unchecked APIs and requires Rust 1.95.0; downstream users should consult the migration guide. CKB’s dependency upgrade is merged for a subsequent node release.

Improvements & Fixes

Node validation and synchronization

After v0.210.0, CKB merged overflow handling and chain-specification validation across epoch calculations, synchronization timers, and protocol limits.

A separate sync-progress fix, extracted from the transaction-pool refactor, prevents reported received-block progress from falling behind the verified chain tip. These changes are merged and await a subsequent node release.

CKB-VM runtime work

The previously reviewed validation-mode proposal landed on develop and was backported to the 0.24 branch. It adds selectable Consensus and Strict modes as API groundwork; consensus mode remains the default, and this change does not itself add strict validation checks.

The 0.24 branch also received an AArch64 frame-marking correction, completing an earlier backport. These changes have not yet appeared in a new CKB-VM release.

Tentacle networking

Tentacle merged QUIC API, configuration, and integration refinements, including clearer configuration errors, consistent transport settings, and a complete service example. This advances the transport library while CKB’s node-level QUIC integration remains open.

For existing connections, yamux write-stall timeouts were restored and receive-window arithmetic was hardened.

Developer tools and contract development

The ckb-tui integration is now merged into ckb-cli. It adds the ckb-cli tui entry point with configurable node endpoints and refresh settings. A new ckb-cli release containing it is still pending.

OffCKB merged fixes for stopping and cleaning up devnet miners, preserving configuration when reading or saving fails, and recognizing contract debug output. Together, they improve devnet lifecycle handling and make contract diagnostics more dependable.

The ckb-std syscall documentation now explains partial loading and error variants more clearly, including when LengthNotEnough represents a successful partial read rather than a failed load.

In Pipeline

Next node release and transaction-pool work

CKB v0.211 release preparation is underway; v0.210.0 remains the latest published node release.

The transactional tx-pool refactor remains open after further refinement and the extraction of the merged sync-progress fix. The larger refactor is still awaiting integration; the smaller fix does not make the redesign a completed feature.

Light-client proofs and input validation

The earlier matched-block retry work has expanded into a draft that binds matched block hashes to their expected heights, alongside retry handling. A separate historical-header proof API is open for review, allowing callers to request proof-backed verification of a specific block-number/hash pair rather than relying on a cached header alone.

Another draft adds checked arithmetic and input validation across network messages, storage, and the WebAssembly API is pending.

DAO treasury voting prototype

The treasury research repository merged a candidate voting implementation with contracts, a TypeScript SDK, and a CLI, followed by SDK end-to-end tests. Subsequent work added a minimum voting amount and tightened proposal transitions: finalization and challenges consume counting cells as transaction inputs, proposal capacity is preserved across updates, and passed proposals are bound to the recipient’s lock.

This remains an experimental voting system in ckb-treasury-lab. Treasury activation, production parameters, and protocol integration remain research and design work.