This release is an optimization of version 3.0.0, which introduced a new hardfork. All nodes should be upgraded before the epoch number reaches 129680000 (estimated on Sep 1). CIP-156 will be enabled when the PoS block number reaches 2754720 (estimated on Sep 1).
Improvements
- Return a detailed version for
conflux --version.
Bug Fix
- Fix the bug of using wrong ws_address to open rpc endpoints.
- Fix
Mismatch between definition and access of rpc-argserror.
RPC Changes
-
eth_getBlockByNumberreturns null when parameter is bigger than latest block.
Note: The Windows version does not support opening the Core Space WebSocket port (
jsonrpc_ws_port,jsonrpc_local_ws_port).
Download
Download “Conflux v3.0.1” here: https://github.com/Conflux-Chain/conflux-rust/releases/tag/v3.0.1
I am a node operator/miner, what do I need to do?
- If you upgrade your node before the epoch number reaches 129680000 (estimated on Sep 1), you need to replace conflux.exe with the new one in Conflux v3.0.1 under the
rundirectory, then restart the node. You are advised to upgrade a running node within 2 days. - If you upgrade your node after the epoch number reaches 129680000 (estimated on Sep 1), you need to delete all data and restart the node.
- If you start a new node, you can download the latest version of Conflux v3.0.1 and run it.
If I have not upgraded to v3.0.0, can I upgrade directly to v3.0.1?
Yes. You can follow the instructions above to upgrade directly to v3.0.1.
What will happen if I do not upgrade the nodes or refuse to upgrade?
If the Conflux node is not upgraded to the latest version, the node will be incompatible with the upgraded Conflux protocol and cannot interact with the latest Conflux network as expected (functions like synchronizing blocks, mining, etc might be disabled).
Thanks to our community for your support!
A sincere thank you to the Conflux community and all the developers in the Conflux ecosystem. Thank you for your hard work, thoughts, and contributions. To a better future!