ckb 0.111.0 (aaa5158 2023-09-14)

[doitian]

Highlights

• This version will activate ckb2023 hardfork in the dev chains.
• There's an ongoing softfork activation since v0.110.1.

Major Changes

• Consensus changes:
  • CKB 2023 edition released (ckb 2023 edition #3917)
  • epoch_duration_target now affects epoch length in Dummy mode (BREAK CHANGE! Consensus: epoch_duration_target now affects epoch length in Dummy mode #4097)
• RPC breaking changes:
  • Set jsonrpc::Ratio as the type of threshold field for DeploymentsInfo and Deployment (RPC: Set jsonrpc::Ratio as the type of threshold field for DeploymentsInfo and Deployment  #3980)
• CLI breaking change:
  • ckb init creates config files even when an unsupported spec is specified (Fix: ckb init creates config files even when an unsupported spec is specified. #4012)

Compatibility Table

Network	Consensus Version	Minimal CKB Version
dev	ckb2023 since epoch 0
testnet	ckb2021 since epoch 3113	v0.101.0
mainnet	ckb2021 since epoch 5414	v0.103.0

See how to connect to various chains in Wiki.

Downloads

OS	Arch	Runtime Dependencies	Package	Sign
macOS	x64	macOS 10.15 or above	zip	PGP
macOS (Portable)	x64	macOS 10.15 or above	zip	PGP
macOS	ARM64	macOS 10.15 or above	zip	PGP
macOS (Portable)	ARM64	macOS 10.15 or above	zip	PGP
Linux	x64	glibc, libstdc++	tarball	PGP
Linux (Portable)	x64	glibc, libstdc++	tarball	PGP
CentOS	x64	glibc, libstdc++	tarball	PGP
CentOS (Portable)	x64	glibc, libstdc++	tarball	PGP
Windows	x64	VC++ Redistributable	zip	PGP
Linux	ARM64	glibc, libstdc++	tarball	PGP
Docker			dockerhub

The .asc files are signatures. It is wise and more secure to check out for the files integrity.

Try the portable variants if the binaries complains about illegal instructions.

Changes since v0.110.2

Features

• ckb 2023 edition #3917 consensus: (BREAKING) CKB 2023 edition (@zhangsoledad)
• rpc(ChainRpc): Add only_committed param for get_transaction #3963 rpc(Chain): Add only_committed param for get_transaction (@eval-exec)
• RPC: Set jsonrpc::Ratio as the type of threshold field for DeploymentsInfo and Deployment  #3980 rpc: (BREAKING) Set jsonrpc::Ratio as the type of threshold field for DeploymentsInfo and Deployment (@eval-exec)
• Update ckb-vm to v0.24.0 #3988: Update ckb-vm to v0.24.0 (@mohanson)
• feat: Suspend support in spawn syscalls #3996: Suspend support in spawn syscalls (@xxuejie)
• feat: let crate ckb-hash support no-std #4002: Let crate ckb-hash support no-std (@yangby-cryptape)
• BREAK CHANGE! Consensus: epoch_duration_target now affects epoch length in Dummy mode #4097 consensus: (BREAKING) epoch_duration_target now affects epoch length in Dummy mode (@eval-exec)
• feat: notify dummy miner for new work #4126: Notify dummy miner for new work (@quake)

Improvements

• refactor(perf): replace sync struct HeaderView with HeaderIndexView #3970 perf: Replace sync struct HeaderView with HeaderIndexView (@quake)
• Reduce PeerStore::load_from_dir_or_default's timecost #4000: Reduce PeerStore::load_from_dir_or_default timecost (@eval-exec)
• refactor: derive implements Clone for cell #4003: Derive implements Clone for cell (@liya2017)
• refactor: split ckb-gen-types from ckb-types #4073: Split ckb-gen-types from ckb-types (@EthanYuan)
• fix(script/spawn): calucate the correct cycles_base #4123 vm(spawn): Calucate the correct cycles_base (@mohanson)
• fix(scripts/spawn): always consume extra_cycles #4127 vm(spawn): Always consume extra_cycles (@mohanson)
• Fix parse RelayV3's message name for metrics service #4129: Fix parse RelayV3's message name for metrics service (@eval-exec)
• fix: keep peer store address unique #4133: Keep peer store address unique (@driftluo)

Bug Fixes

• fix(scripts): set_debug_printer should updates generator's debug_printer #4011 vm: set_debug_printer should updates generator's debug_printer (@mohanson)
• Fix: ckb init creates config files even when an unsupported spec is specified. #4012 cli: (BREAKING) ckb init creates config files even when an unsupported spec is specified. (@eval-exec)
• fix: permanent difficulty mode reward #4015 Fix permanent difficulty mode reward (@zhangsoledad)
• Fix RUSTSEC-2023-0044 warning #4030 Fix RUSTSEC-2023-0044 warning (@eval-exec)
• Add derive(Hash) to ScriptHashType #4151: Add derive(Hash) to ScriptHashType (@eval-exec)

---

This discussion was created from the release ckb 0.111.0 (aaa5158 2023-09-14).

[joshyates1980]

@quake In reference to: this issue, I deleted the entire "ckb 0.111.0-rc12" folder because of local computer issues.

I downloaded "ckb 0.111.0" and executed: ckb init and then ckb run.

I have a new "node_id":"QmVgA1wDAcFJQ12WaS9LQ7wbgrQUfzjqAQ772b5ACetBtu" as of yesterday afternoon so hopefully after some time the CKB Full Node will be fully operational and display on CKB Node Probe

You mentioned that ckb-indexer has been migrated into ckb. Does this mean I do not need to execute ckb run --indexer when I execute Neuron wallet? I'm going to wait until the full node is downloaded before I try Neuron again on this particular computer.

[doitian]

@Keith-CY can you help to answer the question of Neuron?

[Keith-CY]

Hi @joshyates1980
ckb-indexer has been integrated into ckb, so you don't have to run them both, but the indexer module of ckb is not enabled by default, so you still need to run ckb by ckb run --indexer if it's expected to be an external node of Neuron.

Neuron lauches the built-in node with --indexer option, too, ref: https://github.com/nervosnetwork/neuron/blob/9d14ac6e1fe11a80c719c4adb7499cd8af7888a1/packages/neuron-wallet/src/services/ckb-runner.ts#L96

[joshyates1980]

@Keith-CY and @quake : It seems Neuron-v0.110.2 will need to be updated before ckb run --indexer will sync with ckb_v0.111.0. Is this correct?

[Keith-CY]

The compatibility validation is pretty simple that it just checks if the version number of an external CKB node is the same as that of the builtin one, so connecting to a CKB node released after a specific neuron will be alerted because the version numbers are definitely different.

We have introduced a compatibility table in the next version for precise validation. But this case(connecting to an external node released after Neuron) cannot be avoided because the table will be packaged into Neuron instead of being fetched at runtime.

BTW, I have learned that [email protected] has incompatible updates but we haven’t tested it with Neuron, so [email protected] will be set as the builtin node.

Ref:

• Compatibility table: https://github.com/nervosnetwork/neuron/blob/develop/compatible.csv
• Builtin node of [email protected]: Release v0.110.3 neuron#2845

[doitian]

Light Client Protocol Softfork Activation in Mainnet

Field	Value	Note
start	8,282	2023/09/01 00:00:00 utc
timeout	8,552	8,282 + 270
min_activation_epoch	8,648	2023/11/01 00:00:00 utc
threshold	80%

20 hours remaining to reach the min activation epoch.