Conflux v2.1.0-testnet Testnet Upgrade Announcement

The Conflux Testnet (Conflux v2.1.0-testnet) is expected to be upgraded starting from 22:00 Aug.17th to 06:00 Aug.20th, 2022 (GMT+8). This upgrade will simulate most of the mainnet network upgrades.

Download the new fullnode program “Conflux v2.1.0-testnet” at:

Upgrade Details:

Incompatible Changes

Configuration Improvement

  • Add configuration enable_single_mpt_storage to enable storing all history states. Set single_mpt_space = "evm" to only store eSpace states. Note that you’ll need to resync an archive node to reconstruct all the history states.

Storage Improvement

  • Allow snapshots to be removed during recovery. This reduces the disk space requirement for full node sync or recovery.

RPC Improvement

  • Support eth_subscribe and eth_unsubscribe in eSpace RPCs.
  • Add a RPC method cfx_getParamsFromVote to return the currently used value of the voted parameters.
  • Return null for getting skipped transactions and receipts. Whether they will be returned was nondeterministic before, but now they are ensured to be null.

To node operators and miners:

  • If you upgrade your node before Epoch Number reaches 88100000 (around 22:00 Aug.17th, 2022(GMT+8)), you need to replace conflux.exe with the new one in Conflux v2.1.0-testnet under the run directory, then restart the node.
  • If you upgrade your node after Epoch Number reaches 88100000 (around 22:00 Aug.17th, 2022(GMT+8)), you need to delete all data and restart the node.
  • If you start a new node after Epoch Number reaches 88100000 (around 22:00 Aug.17th, 2022(GMT+8)), you can download the latest version of Conflux v2.1.0-testnet and run it.

According to CIP-99 ( ), after this Hardfork, more not-voting terms will be allowed before we force-retire a node, and make the unlock period of a retiring node shorter to allow the node to rejoin the PoS voting faster.

How to upgrade nodes without being forcefully retired

It is recommended to notify the node to stop participating in the election before upgrading. After the node status changes to non-participating, you can shut down the node and upgrade it safely.
The node will automatically rejoin the PoS election after restarting. Specific steps are as follows:

  1. Run the command ./conflux RPC local PoS stop_election to inform the node to stop participating in the election. The node will not end its participation immediately, and the whole process may take several hours. The command returns the block number where the node will stop participating in the election.
  2. Repeat this command to check the status of the node. If the command returns null, then the node has stopped participation in the election. It can be shut down at this time.
  3. Restart the node after the upgrade is completed. The node will automatically re-participate in voting. (Restarting a node will automatically re-execute from the latest checkpoint to the newest block. It may take a long time (several hours), but could be very fast as well)

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 Testnet as expected (functions like synchronizing blocks, mining, etc might be disabled).

To ordinary users:

The upgrade will not affect the normal use of the Conflux Testnet. However, we advise you to avoid using Testnet due to instability and operational delay during the upgrade. There is a possibility that your asset on Testnet will be lost.

According to CIP-94 ( ), after this Hardfork, users can use on-chain DAO voting to decide and update reward parameters without hardfork.

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!