v3.4.0

New

• RPC supports signed Call interface

• P2P dynamic loading black and white list

Modify

• Upgrade TBB version to 2021.8.0

• Optimize the mutex range of read-write locks in synchronization scenarios

Repair

• Fix bug of occasional synchronization failure in extreme scenarios

• Fix bug that only part of the contract is rolled back when the transaction is rolled back

• Fix bug of return value processing in mark transaction operation when viewchange

• Fix the bug that the occasional proxy in the disconnection scenario under pro architecture is empty

• Fix bug of AMOP callback destructor

• Fix thread safety issues in BucketMap extreme cases

• Fix the problem of repeatedly creating multiple task _ groups in Session

• Fix the bug that Response is empty due to coding problems when light nodes send transactions

• Fix the fatal that KeyPage may trigger after deleting data in an empty table

• Historical Version Upgrade

  The “data compatibility version number ([compatibility _ version] of the chain that needs to be upgraded”(#id5)) “is the following version

  • 3.4.x: The data is fully compatible with the current version, and the upgrade can be completed by directly replacing the binary

  • 3.3.x, 3.2.x, 3.1.x, 3.0.x: supports gray-scale upgrade by replacing the binary. If you need to use the new features of the current version, you need to upgrade the data compatible version number. See Document

  • 3.0-rc x: Data is not compatible and cannot be upgraded. Consider gradually migrating your business to the 3.x official version

  • 2.x: data is not compatible, 2.x version is still maintained, you can consider upgrading to the latest version of 2.x

Component compatibility

	Recommended Version	Minimum Version	Description
WeBASE	3.0.2	3.0.2
WeIdentity	v3.0.0-rc.1	v3.0.0-rc.1
Console	3.4.0	3.0.0
Java SDK	3.4.0	3.0.0
CPP SDK	3.4.0	3.0.0
Solidity	0.8.11	Minimum 0.4.25, maximum 0.8.11	The compiler (console) needs to be downloaded according to the contract version
WBC-Liquid	1.0.0-rc3	1.0.0-rc3

Upgrade Method

This operation only supports upgrading version 3.x to this version, and does not support upgrading version 3.0-rc or 2.x。

Query data compatibility version number (compatibility _ version)

Use consoleQuery, such as the current version returned is 3.0.0

[group0]: /apps>  getSystemConfigByKey compatibility_version
3.0.0

Replace Node Binary

Need to beAll NodesGradually replace the binary with the current version。In order not to affect the business, the replacement process can be done in grayscale, replacing and restarting nodes one by one。During the replacement process, the current chain continues to execute with the logic of the old data-compatible version number。After the binary replacement of all nodes is completed and restarted, you need to use the console to modify the data compatibility version number to the current version。

Set the data compatibility version number (compatibility _ version)

Use consoleSet the data compatibility version number. For example, the current version is 3.4.0。

[group0]: /apps>  setSystemConfigByKey compatibility_version 3.4.0
{
    "code":0,
    "msg":"success"
}

Note: If the permission governance function is enabled, you need to use the setSysConfigProposal command

Set successfully, query again, the current version has been upgraded to 3.4.0

[group0]: /apps>  getSystemConfigByKey compatibility_version
3.4.0

The current chain has been upgraded, so far,The chain continues to run with new logicand supports new features。