Conflux Network will be upgraded from 6:00 Feb.21st to 00:00 Mar.2nd, 2022(GMT+8). The Conflux Tethys Network will be upgraded to the Conflux Hydra Network. (Due to the large hash power fluctuation, the estimated completion time might vary.)
Version: Conflux v2.0.0-fix
The new fullnode program download link: https://github.com/Conflux-Chain/conflux-rust/releases
1. Upgrade Content
Incompatible Changes
This Hardfork will activate 8 different CIPs (Conflux Improvement Proposals) including CIP-43, CIP-64, CIP-71, CIP-76, CIP-78, CIP-86, CIP-90, and CIP-92. For more details, see Upgrade CIPs: https://developer.confluxnetwork.org/v2-hardfork/upgrade_list/
We suggest you pay more attention to CIP-43 and CIP-90:
- CIP-43: https://github.com/Conflux-Chain/CIPs/blob/master/CIPs/cip-43.md (Introducing a stand-alone PoS chain, which monitors the process of the PoW chain). For more details, see Conflux PoS Technical Documents: Conflux PoS Technical Documents
- CIP-90: https://github.com/Conflux-Chain/CIPs/blob/master/CIPs/cip-90.md (Introducing a new fully EVM-compatible space. The new space is called Conflux eSpace, and the current space is called Conflux Core). For more details, see Conflux eSpace Kit: Conflux eSpace Kit
Other Incompatible Changes:
- CIP-64: https://github.com/Conflux-Chain/CIPs/blob/master/CIPs/cip-64.md
- CIP-71: https://github.com/Conflux-Chain/CIPs/blob/master/CIPs/cip-71.md
- CIP-76: https://github.com/Conflux-Chain/CIPs/blob/master/CIPs/cip-76.md
- CIP-78: https://github.com/Conflux-Chain/CIPs/blob/master/CIPs/cip-78.md
- CIP-86: https://github.com/Conflux-Chain/CIPs/blob/master/CIPs/cip-86.md
- CIP-92: https://github.com/Conflux-Chain/CIPs/blob/master/CIPs/cip-92.md
RPC Improvements
For more details, see: https://developer.confluxnetwork.org/v2-hardfork/hydra_overview#rpc-changes
PoS RPC
Add a new set of PoS-related RPC methods prefixed with ‘pos’ to retrieve various information about the current PoS chain.
PoW RPC
Hardfork PoW RPC Changes
block
Add a new field to the block structure:
-
posReference: The latest PoS block hash when the PoW block is mined
The block’s custom type has changed from number array to hex string array.
// before
custom: [[1, 2]]
// after
custom: ["0x12"]
cfx_getStatus reponse
cfx_getStatus reponse have two more fields: latestFinalized、ethereumSpaceChainID
New Tag
Add a new EpochNumber tag:
-
latestFinalized: represent the epoch finalized by PoS.
New RPC
Add three new RPCs:
cfx_posEconomicscfx_openedMethodGroupscfx_getPoSRewardByEpoch
txpool-related RPC
Add a new set of txpool-related RPC methods prefixed with ‘txpool’ to obtain various information about the current transaction pool.
Trace RPC improvement
The implementation of Trace has been redesigned so that Trace RPC will be affected. If you use Trace RPC on your own node, you need to resynchronize the data. For more details, see: https://developer.confluxnetwork.org/conflux-doc/docs/RPCs/trace_rpc#v20-trace-breaking-change
eth RPC:
Introduce an Ethereum-compatible ETH RPC through CIP-90. For more details, see: https://developer.confluxnetwork.org/conflux-doc/docs/EVM-Space/evm_space_rpc_compatibility
Bug Fixes
Fix an issue that may slow down the archive node syncing process.
2. Links of ConfluxScan and RPC After the Upgrade
Mainnet Conflux Core Scan: https://www.confluxscan.net
Mainnet Conflux eSpace Scan: https://evm.confluxscan.net (not available)
Mainnet Conflux Core RPC: main.confluxrpc.com
Mainnet Conflux eSpace RPC: evm.confluxrpc.com (not available)
Testnet Conflux Core Scan (Testnet): https://testnet.confluxscan.net/
Testnet Conflux eSpace Scan (Testnet): https://evmtestnet.confluxscan.net/
Testnet Conflux Core (Testnet) RPC: https://test.confluxrpc.com/
Testnet Conflux eSpace (Testnet) RPC: https://evmtestnet.confluxrpc.com/
3. What will happen if I do not upgrade the nodes or refuse to upgrade?
If you do not upgrade your node to the latest version, the node will be incompatible with the newest Conflux Network protocol and will not be able to interact with the Conflux Hydra Network (e.g. synchronize blocks, mining, etc.).
4. I am a PoW node operator/miner, what do I need to do?
You need to upgrade your node before Epoch Number reaches 36935000 or Block Number reaches 92060600 (around 6:00 Feb.21st, 2022(GMT+8))
- Replace conflux.exe with the new one in Conflux v2.0.0-fix, replace tethys.toml with hydra.toml, and then restart the fullnode. Note that you need to enter the password twice during the restart to encrypt the PoS private key. Please keep the password safe. Download link: https://github.com/Conflux-Chain/conflux-rust/releases. How to start a fullnode: How to Start a Fullnode Tutorial（Conflux v2.0.0-fix）
- After Block Number 92751800 (around 09:00 Feb.26th, 2022(GMT+8)), you can start adding pos_config. Reference: Hydra Hardfork Transition Tutorial
- The deadline for adding pos_config is before Epoch Number reaches 37400000 (around 08:00 Feb.27th, 2022). Hardfork upgrade will be completed at this time.
(Due to the large hash power fluctuation, the estimated completion time might vary, it is recommended to complete as soon as possible.)
If you upgrade your node after Epoch Number reaches 36935000 or Block Number reaches 92060600 (around 6:00 Feb.21st, 2022(GMT+8)), you need to clear your data, add pos_config, and restart your node. Reference: Conflux v2.0.0-fix Upgrade Tutorial. To save your time in synchronizing data, we provided a data snapshot for you to download, please refer to "6. How to use data snapshot? "
If you start your new node after Epoch Number reaches 36935000 or Block Number reaches 92060600 (around 6:00 Feb.21st, 2022(GMT+8)), you can download the new version Conflux v2.0.0, and start the node. Reference: Conflux v2.0.0-fix Upgrade Tutorial. To save your time in synchronizing data, we provided a data snapshot for you to download, please refer to "6. How to use data snapshot? "
5. I want to be a PoS node operator, what do I need to do?
You need to upgrade your node before Epoch Number reaches 36935000 or Block Number reaches 92060600 (around 6:00 Feb.21st, 2022(GMT+8))
- Replace conflux.exe with the new one in Conflux v2.0.0-fix, replace tethys.toml with hydra.toml, and then restart the fullnode. Note that you need to enter the password twice during the restart to encrypt the PoS private key. Please keep the password safe. Download link: https://github.com/Conflux-Chain/conflux-rust/releases. How to start a fullnode: How to Start a Fullnode Tutorial（Conflux v2.0.0-fix）
- The PoS registration will start at Epoch Number 36935000 or Block Number 92060600 (around 6:00 Feb.21st, 2022(GMT+8)). Reference: PoS Registration Tutorial
- The PoS registration will close at Block Number 92751800 (around 09:00 Feb.26th, 2022(GMT+8)). After registration closes, you can start adding pos_config. Reference: Hydra Hardfork Transition Tutorial
- The deadline for adding pos_config is before Epoch Number reaches 37400000 (around 08:00 Feb.27th, 2022). Hardfork upgrade will be completed at this time. PoS registration will be reopened at this point.
(Due to the large hash power fluctuation, the estimated completion time might vary, it is recommended to complete as soon as possible.)
If you upgrade your node after Epoch Number reaches 36935000 or Block Number reaches 92060600 (around 12:00 Feb.21st, 2022(GMT+8)), you need to clear your data, add pos_config, and restart your node. Reference: Conflux v2.0.0 Upgrade Tutorial. To save your time in synchronizing data, we provided a data snapshot for you to download, please refer to "6. How to use data snapshot? "
If you start your new node after Epoch Number reaches 36935000 or Block Number reaches 92060600 (around 12:00 Feb.21st, 2022(GMT+8)), you can download the new version Conflux v2.0.0, and start the node. Reference: Conflux v2.0.0 Upgrade Tutorial. To save your time in synchronizing data, we provided a data snapshot for you to download, please refer to "6. How to use data snapshot? "
To prevent forceRetired when your PoS voting node restarts, it is recommended to perform the following operations:
- If you run
./conflux RPC local PoS stop_electionon the PoS node, the node will return either NULL or a future PoS Block Number. After the command has been executed, the node will not apply to join the PoS committee for the next round. - If the Block Number is returned, keep the node running. Run the same command again after the PoS block of the returned block number has been generated (est. several hours later). At this point, NULL should be returned. The node will no longer receive PoS rewards after this block.
- If NULL is returned, the node is safely stopped. The PoS voting process will resume to normal automatically after the node has been restarted (est. 2-3 hours to generate new PoS rewards).
6. How to use data snapshot?
To save your time in synchronizing data, we provided a data snapshot for you to download.
If you haven’t upgraded to the Conflux v2.0.0 node program and restart the node program, you need to clear your data, download the latest data snapshot, and restart the node. To download the latest data snapshot, please visit: https://github.com/conflux-fans/archive-tool
Due to a large amount of network data, the data before and after compression will take up to more than 600G storage space. We highly suggest you use an SSD that has more than 700G of space. You can also try to use two 500G SSD, one for downloading the data snapshot and the other one for uncompressing data snapshot. Notice: DO NOT restart the progress, otherwise you might run up your 500G storage space.
7. I am a DApp developer, what do I need to do?
According to CIP-71 (link: https://github.com/Conflux-Chain/CIPs/blob/master/CIPs/cip-71.md), after the Hardfork, Conflux Network will completely turn off the anti-reentrancy mechanism (same as Ethereum), and deployed contracts need to be aware of whether they are subject to reentrancy attacks.
According to CIP-43 (link: https://github.com/Conflux-Chain/CIPs/blob/master/CIPs/cip-43.md), after the Hardfork, only the staking on the PoS chain generates rewards, and 4% of otherwise staking is no longer profitable.
Since the nodes running PoS have an extra performance burden compared to other nodes, and other parts of the RPCs of PoS nodes may change relatively frequently, it is recommended that PoS nodes only be used for PoS voting service.
Developers using the official Tethys RPC will not be affected.
For exchanges and cross-chain bridges: during the upgrade, we also suggest they temporarily cease the withdrawal and deposit function for at least 48 hours until the network resumes normal operation.
8. What impact will it have on ordinary users?
The upgrade will not affect Conflux Network’s normal usage. However, it is recommended to not conduct any operation during the upgrade to prevent asset loss due to the instability of the network. The operations will most likely result in a huge delay.
According to CIP-43 (link: https://github.com/Conflux-Chain/CIPs/blob/master/CIPs/cip-43.md), after the Hardfork, only the staking to the PoS chain generates rewards. The user’s assets that were otherwise in Governance will not get lost, but continued staking will receive no additional revenue.
Thanks 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!