Conflux Sets August 25 Deadline for v3.1.0 Hard Fork

The transition process is time-sensitive, as failure to update before the target epoch will force operators to purge existing blockchain data and perform a full resynchronization. To facilitate the upgrade, operators must replace a critical settings file and ensure their nodes align with the new, stricter configuration requirements. While the network has provided tools to manage storage and entry points, the update process is designed to be completed within a two-day window.

Central to this release are seven Conflux Improvement Proposals (CIPs). Three of these—CIP-166, CIP-167, and CIP-174—focus on enhancing eSpace compatibility with Ethereum standards. Notably, CIP-167 introduces support for digital signatures commonly used by passkeys, potentially simplifying authentication for decentralized applications. Additional proposals, including CIP-172 and CIP-175, resolve inconsistencies in transaction formatting and cross-space contract permissions.

Beyond feature updates, the release includes a patch for a security vulnerability. To prevent potential exploitation, the network will withhold technical details regarding the fix until the hard fork is fully implemented across the ecosystem. This approach mirrors the project's strategy during its March 2025 security update, which addressed contract address overwriting. Version 3.1.0 also introduces performance refinements, including a real-time transaction monitor and stability improvements to prevent node crashes during shutdown or high-load periods.