ckb 0.103.0 (e77138e 2022-04-11)

[doitian]

Attention that v0.103.0 will activate ckb2021 in mainnet since epoch 5414, at about 2022/05/10 1:00 UTC. See RFC37 and the migration guide for details.

Compatability Table

Network	Consensus Version	Minimal CKB Version
dev	ckb2021 since epoch 0
testnet	ckb2021 since epoch 3113	v0.101.0
mainnet	ckb2019 until epoch 5414	v0.25.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
Linux	x64	glibc, libstdc++	tarball	PGP
CentOS	x64	glibc, libstdc++, openssl	tarball	PGP
Windows	x64	VC++ Redistributable	zip	PGP
Linux	ARM64	glibc, libstdc++	tarball	PGP
Docker			dockerhub

The binaries require following CPU instructions: call (MODE64), cmovbe (CMOV), xorps (SSE1), movq (SSE2)

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

Changes since v0.101.8

Features

• config: activate ckb2021 in mainnet since epoch 5414 #3371: Activate ckb2021 in mainnet since epoch 5414 (@doitian)
  At about 2022/05/10 1:00 UTC.

Bug Fixes

• fix: genesis dep groups should supports relative file path #3343: Genesis dep groups should supports relative file path (@quake)
• fix(ckb cli) add h256 validator for --assume-valid-target and ba-code-hash #3345: Fix(cli) add h256 validator for --assume-valid-target and --ba-code-hash (@chanhsu001)

---

This discussion was created from the release ckb 0.103.0 (e77138e 2022-04-11).

[joshyates1980]

As I am not developing at this time on the Nervos Network, but only executing the CKB full node with version "ckb_v0.101.3_x86_64-pc-windows-msvc" when my computer is in operation, do you still recommend the 0.1.03.0 upgrade? The download of the full chain is big, long, and I want to make sure it is not necessary for my current situation (hence, not developing). Much gratitude, - Josh

[driftluo]

Upgrading is still recommended and it has several reasons:

1. 0.103.0 will perform hardfork and will reject connections from lower versions upon completion
2. 0.101.3 - 0.103.0 with some optimizations and fixes

The upgrade does not need to delete the historical data, just replace the ckb binary, that is, there is no need to resync all the data

[joshyates1980]

Thank you for the suggestion of "just replace the ckb binary." Great tip!