v2.1.0¶
v2.0.x upgrades to v2.1.0
Compatible upgrade : Directly replace the binary of the v2.0.x node with v2.1.0 binary. The upgraded version fixes bugs in v2.0.x but does not enable the new features in v2.1.0. In most cases, it is ok to rollback to v2.0.x after upgrading to v2.1.0. See the last section for more information.
Full upgrade : Refer to Install to build new chain and resubmit all historical transactions to the new node. The upgraded node contains the new features in v2.1.0.
Change description¶
New Features
Update
Support Channel Message v2 protocol
Support to configure node address with domain names
Increase max contract binary size limit to 256KB
Output more detailed log for transaction exceptions
Rename SDK certificate file names generated by build_chain.sh to sdk.crt and sdk.key
Adjust some code structure for better performance
Decrease memory footprint
Fix
Minor channel connection bugs
Compatibility
2.1.0 is forward compatible. Old versions can upgrade to this new version by directly replacing the binaries for bug fixing purpose. But the new features of this version cannot be enabled unless you deploy a new chain with only new binaries from scratch.
| Recommended version | Minimum version | Description | |
|---|---|---|---|
| console | 1.0.5 | 1.0.4 | |
| SDK | 2.1.0 | 2.0.4 | |
| generator | 1.1.0 | 1.1.0 | |
| FISCO BCOS browser | 2.0.0-rc2 | 2.0.0-rc2 | |
| Solidity | up to 0.5.2 | 0.4.11 | |
| amdb-proxy | 2.1.0 | 2.0.2 |
Rollback to v2.0.x after compatible upgrading
After compatible upgrading to v2.1.0, we can rollback by simply replacing fisco-bcos binary file to v2.0.x. If a large contract(binary size between 24K and 256K) is deployed after upgrading, rollback to v2.0.x may lead to block downloading error. In this case, we need to use v2.1.0 fisco-bcos to download blocks until newest block before rolling back.