ckb 0.106.0 (2010923 2022-12-23)

[doitian]

Highlights

Attention that this version requires database migration, please backup the data folder and run the following command:

ckb migrate

This version added better support to estimate the fee rate (#3669). It also has fixed several sync and memory usage bugs. See full changes below.

Compatability Table

Network	Consensus Version	Minimal CKB Version
dev	ckb2021 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
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.105.1

Features

• feat: add rpc estimate_cycles #3669: Add RPC estimate_cycles (@zhangsoledad)
• feat: tuning the locator algorithm #3703: Tuning the locator algorithm (@driftluo)

Bug Fixes

• fix(light-client): subtract overflow when try to get chain root for genesis block #3675 light-client: Subtract overflow when try to get chain root for genesis block (@yangby-cryptape)
• fix(light-client): do not skip the genesis block for last state proofs #3697 light-client: Do not skip the genesis block for last state proofs (@yangby-cryptape)
• fix(tx-pool): potential leaks when MaximumAncestors occurs #3698 tx-pool: Potential leaks when MaximumAncestors occurs (@zhangsoledad)
• Fix tx-pool potential inconsistent after reorg occurs #3706 tx-pool: Fix tx-pool potential inconsistent after reorg occurs (@zhangsoledad)
• fix: indexer CPU usage #3705 indexer: Indexer CPU usage (@zhangsoledad)
• fix: fix logging feature break #3674: Fix logging feature break (@driftluo)
• fix: set recent reject db log file limit to 10 #3681: Set recent reject db log file limit to 10 (@driftluo)
• fix: resolve a long reorg error #3699: Resolve a long reorg error (@quake)
• fix: unknown list should get header from headermap and db #3702: Unknown list should get header from headermap and db (@driftluo)

Misc

• Improve support for cycles access #3684: Improve support for cycles access (@zhangsoledad)

---

This discussion was created from the release ckb 0.106.0 (2010923 2022-12-23).

[joshyates1980]

For all who choose not to run the ckb node on the C: drive, I use my D: drive

[joshyates1980]

Any suggestion on how to fix this error? My main node has not be able to execute for a few weeks now.

[eval-exec]

@joshyates1980

Hello, what's the output of ckb --version ? I suggest you backup your data, then try to repair ckb database by ckb db-repair. Or resync ckb node from scratch.
Let me know if they are not working for you.

[joshyates1980]

[joshyates1980]

@eval-exec Any suggestions? I'm not sure how to troubleshoot this error.
Thanks,

• Josh

[quake]

This error appears to be caused by a hardware error in the disk, could you run chkdsk (a windows builtin command) to scan and fix disk first? Then you may need to delete the ckb's data folder to resync the chain