Repository navigation
CKB Dev Log 2026-11-11 #5367
chenyukang
started this conversation in
Dev Log
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Updates
This cycle (October 14–November 10, 2026) focused on stabilizing light-client data consistency and expanding local developer tooling. Several storage and proof-request fixes landed, while a broader correction for chain reorganizations remains under review. Infrastructure services like the explorer and peer-discovery received targeted reliability updates, and the experimental DAO treasury gained a local end-to-end voting demo.
Key milestones:
Releases & Features
Storage-library compatibility
ckb-db 1.1.2 and ckb-rocksdb 0.21.2 were published on October 30.
ckb-dbpatch relaxes its exact dependency requirement, so downstream projects can adopt the wrapper update. This change does not upgrade the underlying native RocksDB engine.Improvements & Fixes
Light-client storage and proof requests
Note: These fixes are merged into the development branch but await a new light-client release. Existing faulty indexes will require reindexing.
OffCKB extensions and diagnostics
Node and CLI maintenance
ckb-cliadded a formatting fix to prevent out-of-range timestamps or invalid transaction time-locks in RPC responses from crashing the interface during printing.Explorer synchronization and peer-list reliability
ckb-discoverynow properly separates mainnet and testnet peer-list caches and automatically restores message subscriptions after reconnections. Bounded queues and connection limits were also added to prevent unbounded memory growth under heavy load.Hashing libraries for CKB-VM
In Pipeline
Light-client chain consistency
Transaction-pool and storage architecture
DAO treasury voting and local demonstrations
Note: Treasury issuance remains purely experimental and would require protocol agreement and a hardfork to reach production.
Compact membership-proof research
Release preparation and API-server access
ckb-cliauthentication: An open proposal would require a bearer token for calls to the optional API server. If adopted, existing server clients will require updates.All reactions