ckb 0.101.0 (9b81a72 2021-10-20) #3123
doitian
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This release activates ckb2021 since epoch 3113 in the testnet. After that nodes running this version are imcompatible with old versions. However, this version is still compatible with v0.25.0 and above in the mainnet.
See how to connect to various chains in Wiki.
This version has some minor RPC changes:
get_transaction
, which is 2 by default. The response is compatible by setting it to 0.get_peers
RPC.calculate_dao_maximum_withdraw
issue #3055 fixed a bit in the RPCcalculate_dao_maximum_withdraw
.Downloads
The
.asc
files are signatures. It is wise and more secure to check out for the files integrity.Changes since v0.100.0
Features
Bug Fixes
calculate_dao_maximum_withdraw
issue #3055: Resolve rpccalculate_dao_maximum_withdraw
issue (@quake)Improvements
perf: switch global alloc to tikv-jemallocator #3023: Switch global alloc to tikv-jemallocator (@zhangsoledad)
refactor: remove impl cell_provider on store #2914: Remove impl cell_provider on store (@zhangsoledad)
refactor(rpc): change 'connected_duration' duration unit to milliseconds #3028 rpc: Change 'connected_duration' duration unit to milliseconds (@chanhsu001)
BREAKING RPC. Change field
connected_duration
time unit from seconds to milliseconds inget_peers
RPC to make time unit used consistently inget_peers
, RPC clients are suggested to modify time quantity correspond with this change.This discussion was created from the release ckb 0.101.0 (9b81a72 2021-10-20).
Beta Was this translation helpful? Give feedback.
All reactions