CKB Dev Log 2025-10-01

[gpBlockchain]

Updates

Releases & Features

• CKB v0.203.0-rc1 released: https://github.com/nervosnetwork/ckb/releases/tag/v0.203.0-rc1
• Quantum-resistant lock script is now deploying to mainnet: chore: mainnet deployment cryptape/quantum-resistant-lock-script#16
• C version of SMT is now supported: Support feature "smtc" on risc-v target sparse-merkle-tree#56
• Introduced reproducible bootstrap designs for CKB: https://github.com/xxuejie/ckb-bootstrapper/tree/main/projects/ckb

Improvements

• Replaced CKB daemonsize library with deamonsize-me .chore: change daemon dependence #4964
• ckb-std: Improved comments for spawn-related functions Update spawn's comments ckb-std#142
• ckb-vm-contrib: Added documentation Add README.md for some components ckb-vm-contrib#29 and examples Allows collection of VM creation information ckb-vm-contrib#30

Fixes

• Updated the spawn code in ckb-auth for compatibility with mainnet/testnet, including dependency updates and code fixes: Updated many dependencies to make it work right on Meepo ckb-auth#51

In Pipeline…

• CKB v0.203.0 Release CKB v0.203.0 #4960
• ckb crates 1.0
  • Now testing 1.0.0-rc1 with ckb-sdk and ckb-std dependency upgrades
  • PRs are ready feat: Stabilize core crates at 1.0 and decouple from CKB binary versioning #4940
• CKB TUI design: CKB TUI design #4965
  • Overview and Blockchain tabs already completed: https://github.com/officeyutong/ckb-tui
• Validating replacing sled with ckb-rocksdb: Replace SledBackend by ckb-rocksdb #4956
• Ongoing work of implementing bootstrapper CLI tool
• Generic multisig, CoBuild Open Transaction solution without witness refactor, improvement on Anyone-Can-Pay

[tea2x]

Quantum-resistant lock script deployed on mainnet

It's a little misleading word choice here.
People read "deployed" and can think it's already on mainnet while it's not without checking into the pr. Is it?

peace

[chenyukang]

Quantum-resistant lock script deployed on mainnet

It's a little misleading word choice here. People read "deployed" and can think it's already on mainnet while it's not without checking into the pr. Is it?

peace

nice catch, I updated the dev log.