Conflux (CFX) will activate its v3.1.0 hardfork on August 26, introducing CIP-173 along with six other network proposals. The upgrade requires node operators to update their software by August 25 to avoid disruption.
What the upgrade includes
The hardfork bundles seven Conflux Improvement Proposals. CIP-173 is the most prominent, though the network has not released detailed specifications for each proposal in a single public document. The upgrade is part of Conflux's ongoing development cycle, which typically introduces changes to consensus rules, smart contract functionality, or network efficiency.
Node operators running older versions will need to apply the v3.1.0 update before the August 25 cutoff. After that date, nodes that haven't upgraded risk falling out of sync with the main chain, potentially causing transaction processing delays or temporary isolation from the network.
Deadline for node operators
The team behind Conflux has set a clear deadline: all node operators must complete the upgrade by August 25. That gives roughly two weeks from the announcement to prepare. Operators running validator nodes or infrastructure services are advised to test the new software on a testnet before deploying to mainnet.
Conflux has not yet published a detailed migration guide, but the network's documentation page is expected to include step-by-step instructions closer to the date. The upgrade is mandatory for anyone who wants to continue participating in consensus or accessing the latest features.
What happens if you miss the deadline
Nodes that do not update by August 25 will be on a fork that is incompatible with the upgraded chain. They will not be able to process new blocks or transactions after the hardfork activates. The network itself will continue operating normally, but outdated nodes will effectively be left behind.
For users holding CFX tokens or using dApps on Conflux, no action is required — the upgrade happens automatically on the network side. However, anyone running a personal node for privacy or custom purposes should follow the same update process as professional operators.
The hardfork is scheduled to go live at a specific block height, which the Conflux team will announce closer to the date. That block height will determine the exact time of activation on August 26.
