Conflux (CFX) will activate its v3.1.0 hardfork on August 25, introducing a set of CIP upgrades and compatibility changes. The network is asking node operators to update their software by that date to avoid disruption.
What the v3.1.0 upgrade includes
The hardfork brings several CIP (Conflux Improvement Proposal) upgrades and compatibility adjustments. The team has not detailed each CIP in the announcement, but the changes are aimed at improving network functionality and aligning with the broader ecosystem's evolving standards.
Node operators are the key group affected. Anyone running a node on the Conflux network must install the new version before August 25. Missing the deadline means their node could fall out of sync with the upgraded chain, causing disruption to their services.
Why the deadline matters
Hardforks are backward-incompatible upgrades. That means old and new node versions can't talk to each other after the fork. If an operator doesn't update, their node won't be able to validate new blocks or process transactions correctly. The network itself will continue, but the unprepared node will be left behind.
Conflux has not said exactly how many nodes are currently running, but the call to action is clear: update by August 25.
What happens on the day
On August 25, the Conflux network will activate v3.1.0. The exact block height or time has not been specified in the facts, but the update applies to all network participants. Users holding CFX don't need to do anything—their tokens are unaffected—but anyone running infrastructure should test and deploy the new version in time.
Operators can check the official Conflux documentation for the release details and installation instructions. The clock is running.
