Conflux v3.0.0 Network Hardfork Upgrade Announcement（August 1, 2025）

ConFi-Conflux · 6 August 2025 02:34

This release introduces a new hardfork. All nodes should be upgraded before the epoch number reaches 129680000 (estimated on Sep 1). CIP-156 will be enabled when the PoS block number reaches 2754720 (estimated on Sep 1).

Conflux is planning to activate and implement modifications of 8 different CIPs (improvement proposals), including CIP-150, CIP-151, CIP-152, CIP-154, CIP-156, CIP-165, CIP-645 and CIP-7702, as well as related RPC updates in the next Hardfork system upgrade.

For more details, please refer to the following link: https://www.confluxdocs.com/docs/general/hardforks/v3.0

CIP Changes

These CIPs are mainly divided into the following categories:

EVM Compatibility: CIP-150, CIP-151, CIP-152, CIP-165, CIP-645, CIP-7702
Bug Fix: CIP-154
Specification Adjustment: CIP-156

The following is a brief introduction of these CIPs.

CIP 150: This CIP replicates EIP-3541, which disallows deploying new code that starts with the 0xEF byte.
CIP 151: This CIP replicates EIP-6780, which prevents contracts from being destroyed by SELFDESTRUCT in most cases, with the only exception being the destruction of a contract within the same transaction as its creation.
CIP 152: This CIP replicates EIP-3607, which addresses a potential security issue where an EOA could share the same address as a contract due to a collision attack. Specifically designed EOAs with code (like EIP-7702), are not affected by this restriction.
CIP 154: This CIP addresses an implementation error in CIP-142, which incorrectly implemented the TLOAD opcode as SLOAD.
CIP 156: This CIP changes the penalty of PoS malicious behavior from permanent stake forfeiting to temporary stake locking.
CIP 165: Introduces precompiles for BLS12-381 curve operations as defined in EIP-2537, enabling efficient execution of tasks such as BLS signature verification.
CIP 645: This CIP proposes aligning Conflux eSpace’s behavior with Ethereum’s EVM to ensure compatibility with Ethereum development tools and provide a consistent experience for developers. It also addresses the impact of new EIPs on Conflux Core Space. Additionally, this CIP addresses discrepancies found during Ethereum behavioral alignment tests.
CIP 7702: This CIP introduces EIP-7702 to Conflux eSpace.

RPC changelog

Note: To enable the RPC service for eSpace, you need to open both the HTTP (jsonrpc_http_eth_port) and WebSocket (jsonrpc_ws_eth_port) ports in the configuration file.

Below RPC add support for EIP-7702 tx:

eth_call & eth_estimateGas
transaction related RPCs: eth_getTransactionByHash, eth_blockByNumber, eth_blockByHash

Misc changes:

Support gasFee in transaction receipt for espace RPC
eSpace block.gasLimit change to half of the consensus gas limit, add block.espaceGasLimit to return the real gas limit for eSpace transactions.
eSpace parity style trace RPCs updates:
a. Trace RPC methods now compatible with parity and erigon, including trace_block, trace_transaction, trace_filter, this is a API breaking change
b. Two new RPCs trace_get and trace_blockSetAuth are added
c. trace_blockSetAuth is a Conflux specific RPC used to get the block set auth result, check trace doc for details.
d. These trace methods now support SelfDestruct(Suicide) trace, to access historical selfdestruct transaction data, a resync of the data is required.
eSpace now support geth style txpool namespace methods, including: txpool_status, txpool_inspect, txpool_content, txpool_contentFrom
eth_call, eth_estimateGas add support for stateoverride feature.

Download

Download “Conflux v3.0.0” here: https://github.com/Conflux-Chain/conflux-rust/releases/tag/v3.0.0

I am a node operator/miner, what do I need to do?

If you upgrade your node before the epoch number reaches 129680000 (estimated on Sep 1), you need to replace conflux.exe with the new one in Conflux v3.0.0 under the run directory, then restart the node. You are advised to upgrade a running node within 2 days.
If you upgrade your node after the epoch number reaches 129680000 (estimated on Sep 1), you need to delete all data and restart the node.
If you start a new node, you can download the latest version of Conflux v3.0.0 and run it.

What will happen if I do not upgrade the nodes or refuse to upgrade?

If the Conflux node is not upgraded to the latest version, the node will be incompatible with the upgraded Conflux protocol and cannot interact with the latest Conflux network as expected (functions like synchronizing blocks, mining, etc might be disabled).

Thanks to our community for your support!

A sincere thank you to the Conflux community and all the developers in the Conflux ecosystem. Thank you for your hard work, thoughts, and contributions. To a better future!