ckb 0.111.0-rc12 (a15a467 2023-09-07)

[doitian]

This is an RC version to preview the changes in the next release.

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

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

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.111.0-rc11

v0.111.0-rc11...9fb20c1

---

This discussion was created from the release ckb 0.111.0-rc12 (a15a467 2023-09-07).

[joshyates1980]

I am attempting to RUN CKB full node with version 0.111.0-rc11, but have the following errors:

I received the same errors when I tried to RUN CKB init command with version ckb_v0.110.1_x86_64-pc-windows-msvc.

My goal is to run a full node on this old laptop 24/7.
Here are my laptop specs:

[quake]

I am attempting to RUN CKB full node with version 0.111.0-rc11, but have the following errors:

could you install the latest Microsoft Visual C++ Redistributable for Visual Studio and try it again?

[joshyates1980]

Thank you, this corrected the issue and I can now RUN CKB full node.

[joshyates1980]

@quake , I have tried to sync full node for many days on my older computer. After I restarted my computer, and attempted to run ckb --indexer, I received this error:

How can I continue my full node, it's around 60%.

[quake]

@joshyates1980 it's a known issue of 0.110.1, it may take a long time to starting sync again after service restart, 2 ~ 15 mins, depends on your disk IO performance, could you wait a while to see if it's normal? And this bug has been fixed in 0.111, I think it will be released in this week.

[quake]

btw, ckb-indexer has been migrated into ckb already in recent recent releases, you may use ckb run --indexer to start the built-in indexer service.