This version is compatible with v0.25.0 and above. However, it is recommended to upgrade the node, since we will only release security patches based on the latest release.
See how to connect to various chains in Wiki.
The version v0.100.0 will bring incompatible changes for the next hard fork but it will not activate the hard fork for testnet and mainnet. So it is compatible with the current testnet and mainnet.
- The block header as a new field
extra_hash
, which replaceduncles_hash
. - The block has a new field
extension
but no blocks may set it before the hard fork activation. - The field
hash_type
has a new allowed value "data1" but it is invalid before the hard fork activation. - The default value of the parameter
OutputsValidator
in the JSON RPCsend_transaction
iswell_known_scripts_only
now. See #2821 for details.
Downloads
OS | Arch | Runtime Dependencies | Package | Sign |
---|---|---|---|---|
macOS | x64 | macOS 10.12 or above | zip | PGP |
Linux | x64 | glibc, libstdc++ | tarball | PGP |
CentOS | x64 | glibc, libstdc++, openssl | tarball | PGP |
Windows* | x64 | VC++ Redistributable | zip | PGP |
Docker | dockerhub |
* Windows support is experimental.
** The binaries require following CPU instructions: call (MODE64), cmovbe (CMOV), xorps (SSE1), movq (SSE2)
The This version contains the fork features in ckb2021 which are disabled in testnet and mainnet.
#2715 hardfork: ckb2021 hardfork features (@yangby-cryptape)
#2756 hardfork: Ckb2021 hardfork features (vm related part) (@yangby-cryptape)
#2818 hardfork: Change field "hash_type" to an enumerated type (@yangby-cryptape)
BREAKING CHANGES: Revert breaking changes which were introduced in #2756.
#2797 hardfork: Reject vm1 lock script before hardfork started to keep compatible with old clients (@yangby-cryptape)
#2798 hardfork: Remove the header deps immature rule (@yangby-cryptape)
#2819: Only send notifications when service is stated (@zhangsoledad)
#2817: Prepend the binary version to BlockAssemblerConfig message (@quake)
#2821: Change default #2792 hardfork: Verify the epoch in since more strictly (@yangby-cryptape)
See more in nervosnetwork/rfcs#223
#2776 hardfork: Rename JSON RPC field "uncles_hash" to "extra_hash" (@yangby-cryptape)
#2799: Resumeble verification, which removes the cycles limit to relay tx (@zhangsoledad)
#2854: Better tips for "migrate" subcomamnd (@yangby-cryptape)
#2849: Remove old version peer from peer store on fork (@driftluo)
#2879 hardfork: Add a new field "hardfork_features" to the return of RPC method "get_consensus" (@yangby-cryptape)
#2656: Persistent tx-pool data into a file when it has been shutdown (@quake)
#2921: Reduce cellbase maturity on staging spec (@keroro520)
#2963: Update ckb-vm to 0.20.0-rc4 (@mohanson)
ckb-vm 0.20.0-rc4 release note: https://github.com/nervosnetwork/ckb-vm/releases/tag/0.20.0-rc4
#3004: Update ckb-vm to 0.20.0-rc5 (@mohanson)
Contains a bug fix, see release notes below:
https://github.com/nervosnetwork/ckb-vm/releases/tag/0.20.0-rc5
#2785: Put migration version (@zhangsoledad)
A bug introduced by 220464f, cause the migration version do not put in the new created DB.
#2827: Fix peer store evict (@driftluo)
Originally, only the data in the largest group was considered, but now it is changed to traverse at least half of the groups
#3011: Shouldn't override the #2787: Put migration version (@zhangsoledad)
#2833: Display full path for deprecated fields in warning messages (@yangby-cryptape)
#2856: Touch #2857: Fix the status marking problem of header sync (@driftluo)
#2877: Don't panic when the database is created by a higher version executable binary (@yangby-cryptape)
#2894: There may be competition between header sync and eviction (@driftluo)
#2897 metrics: There is no reactor running (@yangby-cryptape)
#2923: Callback potentially incorrect trigger on concurrent context (@zhangsoledad)
#2924 test: Make sure testnode graceful shutdown basic sync (@zhangsoledad)
#2932: Persisted test wait tx-pool ready (@zhangsoledad)
#2950 reset-data: The argument #2971: Snapshot cycles calculation (@zhangsoledad)
#2755: Avoid unnecessary db creation (@zhangsoledad)
#2685: Replace #2736: Move state flag to We are using 3 fields #2707: Use KeyedPriorityQueue to replace BTreeMap/HashSet (@quake)
#2791: Verify the epoch in block headers explicitly (@yangby-cryptape)
The data of epoch in bytes is not same as the #2822: Compatibility policy for configuration files (@yangby-cryptape)
Deny unknown configuration items.
To avoid several kinds of mistakes, for example, typos.
Allow deprecated configuration items, but they will be ignored; and warning messages will be output. The default configuration files will not include any deprecated configuration items.
The default configuration files will not enable any experimental configuration items.
#2770: Use community contributed site for script error codes (@doitian)
#2779: Give an unique id to each global runtime thread (@yangby-cryptape)
#3006 rpc: Change struct from "TxPoolVerbosity" to "TxPoolEntries… (@chanhsu001)
Breaking change for using ckb crates.
#2863: Avoid duplicate cell check (@zhangsoledad)
#2870: Replace metrics-rs with opentelemetry-rust (@yangby-cryptape)
#2925: Enum tuple struct (@zhangsoledad)
#2948: Remove dependency on tempfile in ckb-resource (@chanhsu001)
.asc
files are signatures. It is wise and more secure to check out for the files integrity.
Changes since v0.43.2
Features
See [CKB-RFCs PR 240: RFC: Remove header deps immature rule](https://github.com/nervosnetwork/rfcs/pull/240)
OutputsValidator
to well_known_scripts_only
(@quake)
epoch_index
is less than epoch_length
or both epoch_index
and epoch_length
are zero.
Bug Fixes
log.file
after touch it (@yangby-cryptape)
last_txs_updated_at
in tx pool (@zhangsoledad)
--network-peer-store
couldn't work (@yangby-cryptape)
Improvements
RwLock/Mutex<HashMap/HashSet>
with DashMap (@quake)
HeadersSyncState
enum (@quake)
sync_started
/ sync_connected
/ not_sync_until
in the headers sync process, this PR refactored them to a state machine enum HeadersSyncState
EpochNumberWithFraction
, which causes a few unintended consequences.
After several versions, if these deprecated items satisfied any of the following conditions, they will be fully removed (denied):