ckb 0.117.0 (4920ecf 2024-07-29)

[doitian]

Highlights

There are two improvements applied for the RPC:

• Add include_tx_pool: Option<bool> param to ChainRpcImpl::get_live_cell' #4454: Add include_tx_pool: Option<bool> param to ChainRpcImpl::get_live_cell' (@eval-exec)
• Add assume_valid_target_reached: bool to NetRpc::sync_state  #4486: Add assume_valid_target_reached: bool to NetRpc::sync_state (@eval-exec)

Please note that these changes are considered breaking changes and may cause compatibility issues with older versions of RPC clients.

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.

Default assume valid target

• Mainnet: HASH
• Testnet: HASH

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.116.1

Features

• Add include_tx_pool: Option<bool> param to ChainRpcImpl::get_live_cell' #4454: Add include_tx_pool: Option<bool> param to ChainRpcImpl::get_live_cell' (@eval-exec)

  This is a breaking change to the RPC.

• Add assume_valid_target_reached: bool to NetRpc::sync_state  #4486: Add assume_valid_target_reached: bool to NetRpc::sync_state (@eval-exec)

  This is a breaking change to the RPC.

Bug Fixes

• Fix rich indexer partial query by args performance issue #4484: Fix rich indexer partial query by args performance issue (@EthanYuan)
• Fix websocket subscription performance issue #4505: Fix websocket subscription performance issue (@chenyukang)

Improvements

• chore: tweak max_ancestors_count #4487: tweak max_ancestors_count (@zhangsoledad)
• Use standalone runtime for RPC service #4459: Use standalone runtime for RPC service (@chenyukang)
• Modify the record scope of tx-pool reject record and fix rule for orphan tx. #4511: Modify the record scope of tx-pool reject record and fix rule for orphan tx. (@zhangsoledad)
• Backport #4527 Early return process_fetch_cmd if ckb received exit signal #4531: Early return process_fetch_cmd if ckb received exit signal (@eval-exec)

---

This discussion was created from the release ckb 0.117.0 (4920ecf 2024-07-29).

[joshyates1980]

I use ckb run --indexer command. I just upgraded to ver 0.117. Does the Indexer have to be rebuilt after each upgrade: INFO ckb_indexer_sync append 000000 to xxxxxxx? Also, is there a particular reason why CKB Node Probe cannot be included in upgrades? I manually edit the files (which is fine): https://nodes.ckb.dev/getConnectedInstruction

[eval-exec]

I use ckb run --indexer command. I just upgraded to ver 0.117. Does the Indexer have to be rebuilt after each upgrade: INFO ckb_indexer_sync append 000000 to xxxxxxx? Also, is there a particular reason why CKB Node Probe cannot be included in upgrades? I manually edit the files (which is fine): https://nodes.ckb.dev/getConnectedInstruction

Could you please provide your indexer related configuration section from the ckb.toml file?

[quake]

I use ckb run --indexer command. I just upgraded to ver 0.117. Does the Indexer have to be rebuilt after each upgrade: INFO ckb_indexer_sync append 000000 to xxxxxxx?

Re-indexing is only needed if the indexer storage schema changes, what was the version of ckb before you upgraded?

[joshyates1980]

ver 0.116.1

[quake]

there are no data migration between 0.116.1 and 0.117.0, we cannot reproduce this bug.