Conflux (CFX) Initiates v3.0.1 Network Hardfork Upgrade
Luisa Crawford Aug 11, 2025 19:59
Conflux (CFX) announces the v3.0.1 network hardfork upgrade, urging node operators to upgrade before September 1, 2025, to ensure network compatibility and functionality.
Conflux (CFX) Network has officially announced the release of its version 3.0.1, marking a significant hardfork upgrade aimed at optimizing the functionalities introduced in version 3.0.0. According to the Conflux Forum, this upgrade is essential for all node operators, who are advised to update their nodes before the epoch number reaches 129680000, estimated to occur on September 1, 2025.
Key Improvements and Bug Fixes
The v3.0.1 upgrade brings several enhancements to the Conflux network. Notably, it returns a detailed version for the conflux --version command, providing more information to node operators. Additionally, crucial bug fixes have been implemented, including resolving the issue of incorrect ws_address usage for opening RPC endpoints and addressing the Mismatch between definition and access of rpc-args error.
RPC Changes and Compatibility
One significant change in the RPC protocol is that the eth_getBlockByNumber method now returns null if the parameter exceeds the latest block number. It is important to note that the Windows version does not support opening the Core Space WebSocket port, which includes jsonrpc_ws_port and jsonrpc_local_ws_port.
Instructions for Node Operators
Conflux has provided detailed instructions for node operators regarding the upgrade process. For those updating before the epoch number reaches 129680000, the updated conflux.exe should replace the existing one in the Conflux v3.0.1 run directory, followed by a node restart. Operators are urged to complete this upgrade within two days to ensure seamless network operations.
If the upgrade occurs after the specified epoch number, all data must be deleted before restarting the node. New node operators can directly download and run the latest version of Conflux v3.0.1.
Consequences of Non-Compliance
Failure to upgrade nodes to the latest version will result in incompatibility with the Conflux protocol, leading to potential disruptions in block synchronization and mining activities. Operators are strongly encouraged to proceed with the upgrade to maintain network functionality.
The Conflux team extends gratitude to its community and developers for their continuous support and contributions, emphasizing the collective effort towards enhancing the network's performance and reliability.
Image source: Shutterstock.jpg)
