CKB Dev Log 2026-07-22 #5288
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
The primary focus of this cycle is release stabilization and system hardening.
Over the past month, we shipped CKB v0.208.0, addressed security and dependency cleanup, improved RPC and mining-related operator behavior, and kept larger architecture work moving through review.
Across the wider stack, CKB-VM continued cleanup and compatibility work, alongside a few new educational deep-dives published. light client received another round of bounds and panic-path hardening. Tentacle released 0.7.6 and kept networking reliability/security follow-ups under review. CKB DAO treasury/voting research moved further from design into executable PoC work.
Several large pieces remain intentionally in pipeline, especially the tx-pool pipeline architecture, Guix reproducible release flow, QUIC ServiceBuilder integration, and additional network/VM hardening.
Releases & Features
CKB v0.208.0 release
Published on July 15, 2026, this regular minor release includes live-cell RPC response enhancement, signing key update, Tentacle dependency upgrade, dependency security updates, and Windows release packaging fixes.
Miner notify authentication
CKB added optional bearer-token authentication for miner notify mode. This allows nodes to send an authorization token with block-template notifications, and miners can reject requests with missing or incorrect tokens, while keeping backward compatibility when no token is configured.
CKB DAO treasury and voting PoC
The DAO treasury/voting research advanced into a public proof-of-concept phase. The
ckb-treasury-labincludes the implementation of the vote-typescript contract, SDK, tools, and e2e tests.For now, this remains research/PoC work rather than a confirmed CKB protocol change.
Tentacle 0.7.6 release
Released on July 9, 2026, v0.7.6 includes QUIC groundwork from earlier PRs, plus reliability and hardening fixes around X25519 validation, yamux back pressure, secio logging, randomized yamux stream IDs, runtime compatibility, and half-close handling.
Improvements & Fixes
CKB core
CKB continued public security and reliability hardening across relay, networking, tx-pool verification, workflow permissions, dependencies, test stability, and CI infrastructure.
CKB light client security and bounds checks
CKB light client received another batch of defensive fixes around checked arithmetic, block-filter indexing, relayer peer-id extraction, and reorg boundary handling.
CKB-VM and script runtime
We continued cleaning up CKB-VM execution-path and improving decoder/trace correctness work, including AArch64 trace compatibility, RV32 illegal-shift decoding, slow-path removal, A-extension removal, and Rust version alignment.
We expanded the educational materials. New notes published, explaining macro-ops fusion, the B extension, and CFI-related execution concepts.
Networking reliability and security
Tentacle stabilized several transport and stream-handling paths for the v0.7.6 release, including yamux delivery backpressure, secio logging, stream ID randomization, runtime compatibility, and half-close notification behavior.
Tooling and developer experience
CKB-CLI hardened H160 parsing by replacing an unwrap path with proper error handling.
In Pipeline
Tx-pool pipeline architecture
The tx-pool pipeline refactor remains in review with green CI as of July 22. It separates transaction processing into classify, pre-check, resolve, verify, and submit stages, preserves the legacy path behind a feature gate, and reports great benchmark gains for secp256k1 transaction throughput.
Guix reproducible release flow
The Guix-based reproducible release flow remains under review. The PR adds pinned Guix build scripts, Cargo source materialization from
Cargo.lock, path remapping for reproducibility, and multi-platform release build support.CKB core follow-ups
Ongoing work includes: tx-pool pipeline review, onion dependency cleanup, JSONL import error propagation, workflow hardening, and dependency updates.
CKB-VM and light-client follow-ups
Active reviews for the VM and light-client are focused on ensuring MOP fusion correctness, contributor documentation, and additional light-client message/checkpoint validation.
Tentacle QUIC and network hardening
Tentacle’s review queue remains busy with ongoing work on the QUIC ServiceBuilder integration, connection limits, backpressure, yamux keepalive behavior, idle/session cleanup, and discovery-input validation.
Treasury and proposal-script research
The CKB DAO treasury and proposal-script works remain in the research/prototype stage. The current direction is to benchmark and refine proposal/voting scripts before making any protocol-level decision.
All reactions