Conflux (CFX) CFX Releases v3.0.3 Node Upgrade With CIP-166 Opcode

Conflux (CFX) Network pushed its v3.0.3 node upgrade on April 9, 2026, delivering seven bug fixes and introducing the CIP-166 Count Leading Zeros opcode. Unlike hard forks, this stability-focused release doesn't require immediate action from node operators—though the development team recommends upgrading.

CFX currently trades at $0.05, up roughly 1% over 24 hours, with a market cap near $261 million. The token gained 12% in mid-March following a technical breakout from its downtrend.

Critical Bug Squashed

The most significant fix addresses a PoS force-retire overflow bug that caused nodes to panic with a "subtract with overflow" error when force-retire events triggered earlier than expected. For validators running Conflux's hybrid PoW/PoS consensus, this patch eliminates a potential crash scenario.

Other notable fixes include:

• CIP-78 sponsor flag corrections for reverted transactions during testnet replay
• A fee_history deadlock resolved through read_recursive implementation
• Gas limit maintenance errors in the transaction packing pool
• eth_estimateGas now properly handles non-existent sender addresses

Developer-Facing Changes

The upgrade adds CIP-166, implementing a Count Leading Zeros opcode—a low-level optimization useful for certain cryptographic operations and mathematical computations. Developers building on Conflux's EVM-compatible eSpace environment also get a new state dump subcommand for exporting all eSpace accounts to JSON.

RPC improvements include pending tag support for eth_blockByNumber and an accumulatedGasUsed field in transaction receipts. The Core Space trace API received structural updates removing Option wrappers from several fields.

Infrastructure Modernization

Under the hood, Conflux bumped its Rust compiler requirement to version 1.90 and updated the revm and c-kzg dependencies. The team also established GitHub Actions CI/CD workflows across Linux, macOS, and Windows—a sign of maturing development infrastructure.

What Node Operators Should Know

The upgrade process remains straightforward: stop your node, swap the conflux executable with the v3.0.3 binary from GitHub, and restart. New node operators can download v3.0.3 directly.

Conflux explicitly stated this upgrade targets stability improvements only. "It'll be fine if you do not upgrade to this version," the announcement notes—meaning no consensus changes or hard fork deadlines.

For a network that's built partnerships with China Telecom and integrated with social platform XiaohongShu, maintaining node stability supports Conflux's positioning as enterprise-ready infrastructure. The next meaningful catalyst for CFX traders will likely come from ecosystem expansion rather than core protocol changes.