Conflux Network has set Aug. 25 as the expected activation date for its v3.1.0 hard fork, a mandatory upgrade tied to epoch 155140000. The release bundles seven Conflux Improvement Proposals, or CIPs, along with a security fix whose details will remain private until the network has completed the transition.
The update affects all node operators. Conflux said systems that do not move to v3.1.0 before the target epoch risk falling out of compatibility with the chain, which could leave them unable to download new blocks, process transactions, or continue mining.
Upgrade deadline is tied to a network epoch
In an Aug. 3 announcement, Conflux said every node must install version 3.1.0 before the blockchain reaches epoch 155140000, which the network expects on Aug. 25. Rather than setting a fixed clock time, Conflux used an epoch target because the exact activation point depends on block production speed.
Operators that upgrade before the deadline can install the software and restart their nodes through the normal process. Conflux advised completing the procedure within two days from the start of the update.
Those that wait until after the target epoch face a more disruptive recovery path. According to Conflux, they will need to delete existing blockchain data, install the new release, and resync the network history from scratch.
Configuration changes are part of the release
The hard fork does not only require a software swap. Conflux said operators must also replace an important configuration file with the updated version included in the v3.1.0 release. Older copies will fail under the stricter validation checks introduced in the new software, preventing a node from starting.
Operators who had previously customized storage locations or logging settings can carry those choices into the replacement file. Conflux also published an updated list of bootnodes, the entry points nodes use when first connecting to peers on the network.
An additional optional setting is available for operators that want to reduce storage use. Conflux said enabling it will lengthen the first restart because the node has to rebuild a current state record, though later restarts should return to normal timing.
Seven CIPs include Ethereum compatibility and transaction fixes
The v3.1.0 hard fork is set to activate CIP-166, CIP-167, CIP-172, CIP-173, CIP-174, CIP-175 and CIP-176. Conflux said three of those changes are aimed at bringing eSpace, its Ethereum-compatible environment, closer to current Ethereum standards and developer expectations.
CIP-166 introduces an operation for counting leading zero digits in a value, a low-level change intended mainly for developers but one that keeps Conflux aligned with a recent Ethereum standard. CIP-167 adds support for checking a digital signature type used by passkeys and online identity systems, a change that could help developers build wallets and applications with alternative sign-in methods. CIP-174 places limits on data passed into a computation-heavy feature and raises the transaction fee for using it.
The remaining proposals address broader network behavior. CIP-172 requires every transaction included in a block to use a single approved format, preventing multiple identifying codes for the same transaction. CIP-175 fixes permission recognition in certain calls between Core Space and eSpace, while CIP-176 corrects how the network prepares stored data for use during a transaction.
Staking change follows a day later, security details come later still
One of the seven proposals, CIP-173, has a separate activation point. Conflux said it is expected to take effect at block 3749400 on Aug. 26, one day after the main upgrade deadline. The proposal changes how disputes involving proof-of-stake validators are reviewed and extends an existing lock on staked CFX to validators that have begun withdrawing their deposit.
Version 3.1.0 also contains what Conflux described as a fix for a security weakness. The network said it will withhold the technical details until after the hard fork is complete, arguing that early disclosure could expose nodes that have not yet upgraded to targeted attacks.
The next confirmed step is the network reaching epoch 155140000, when operators are expected to already be on v3.1.0. After the fork is completed, Conflux has said it will disclose more about the private security patch.
Source: crypto.news