v2.3.x upgraded to v2.4.0

  • Compatible upgrade :Directly replace the binary of the v2.3.x node with the v2.4.0 binary , the upgraded version fixes bugs in v2.3.x, and includes 2.4.0 dynamic group life cycle management function, network statistics function, but will not enable all the features of 2.4.0, in normal scenarios, you can roll back to v2.3.x. For the rollback method, refer to the last section of this article.

  • Full upgrade :Refer to Installation to build a new chain and resubmit all historical transactions to the new node. The upgraded node includes new features in v2.4.0

  • v2.4.0 Release Note

Change description

New features


  • The minimum requirement of CMake is modified to 3.7, supporting multi-source download of dependent libraries


  • Fix the problem that the ecRecover interface is not available in the OSCCA-approved cryptography mode

  • Fix the inconsistent return value of sha256 interface in OSCCA-approved cryptography mode and non-OSCCA-approved cryptography mode


Forward compatible, The old version can directly replace the program upgrade, the replaced node fixes the bug in v2.3.x, and includes 2.4.0 dynamic group life cycle management function and network statistics function, to enable all new features in v2.4.0, you need to rebuild the blockchain.

Recommended version Minimum version Description
console 1.0.9 1.0.4
SDK 2.4.0 2.0.4
generator 1.4.0 1.1.0
FISCO BCOS browser 2.0.2 2.0.0-rc2
Solidity up to 0.5.2 0.4.11
amdb-proxy 2.3.0 2.0.2

Compatibility mode rollback to v2.2.x method

After a node is upgraded from v2.3.x to v2.4.0 in compatibility mode, the rollback can be completed directly by replacing the node binary back to v2.3.x.