What happened
Conflux Network confirmed Wednesday that its v3.1.0 client release will activate via hard fork on Aug. 25, 2026, according to a notice first reported by Crypto.News. The upgrade is not optional. Every validator, full node, and archive node has to install the new binary before the fork block or drop off the canonical chain.
The release packages seven Conflux Improvement Proposals into a single activation. Alongside the public CIPs, the team is shipping a private security fix that will stay undisclosed until after the network migrates, a standard playbook lifted from Ethereum core dev practice: patch first, publish the vulnerability details only once the vulnerable clients are off the network. Conflux hasn't named which subsystem the patch touches or how severe the underlying issue is.
Exchanges and infrastructure providers running Conflux nodes were notified through the same channel. The client binary is available now, giving operators roughly twelve days to test, stage, and roll the update across their fleets.
Why it matters
Hard forks are the moment a proof-of-stake network can bundle protocol changes that a soft fork can't carry, and Conflux is using v3.1.0 to clear a backlog of seven CIPs in one shot rather than dripping them out across quarterly releases. Bundling reduces coordination overhead for node operators, but it raises the stakes for any single bug in the release: a chain split at activation drags every CIP down with it.
The private security fix is the more interesting piece. Networks don't announce silent patches unless the underlying bug is meaningful enough to justify the coordination cost of a mandatory upgrade window. Conflux's decision to disclose the existence of the fix while withholding details signals the team believes public description before activation would create an exploit window wider than the risk of a rushed rollout.