This website is the Beta Version of Conflux Governance, and the linked network is the Conflux testnet (version: Conflux v2.0.0-testnet). The data is used for the test of the Conflux testnet. This network is only used for testing purposes. During the test, there is no guarantee that the network service will not be interrupted, and there is no guarantee for the timeliness, security, and accuracy of the network service.
Notice 1: Some operations may cause your pending staking token to be permanently locked, including but not limited to:
- Modify the code of Conflux-rust, resulting in a certain kind of consensus-breaking behavior in your PoS account.
- Use the same PoS private key and address for running multiple PoS nodes. (Therefore, it is not recommended to copy the PoS private key file elsewhere.)
- The unauthorized usage of the PoS private key by other parties will also result in the above phenomenon.
- Lose the PoW address private key bound to the PoS private key, thus failing to issue the unlocking instruction.
Note: If the PoS private key is lost but not stolen, it will not cause capital loss. Simply use the PoW address to send the unlocking instruction to recover the fund.
Notice 2: Some operations may cause your staking token to automatically enter the unlocking state, including but not limited to:1. After being selected into the PoS Committee, fail to bear the responsibility of a committee member to vote for the PoS block for over one epoch (about one hour) due to the program abort, network failure, malicious attack, or other reasons.
Note: In this case, when all staking is completely unlocked, the PoS address will return to normal.
Notice 3: Some operations may result in not getting any interest, including but not limited to:1. Fail to launch the PoS node or connect to the PoS network.
Notice 4: If you transfer the CFX token to another contract / private key address, the contract operator / private key owner shall be fully responsible for the security of the fund.
Notice 5: After sending the unlocking instruction, the actual unlocking time of the token shall be subject to the later one of the two given dates:
- 7 days after sending the unlocking instruction
- 7 days after locking the token is locked in multiple batches, the unlocking time of each batch shall be calculated separately.
If you upgrade your node before Epoch Number reaches 55095000 or Block Number reaches 68845000 (around 10:00 Dec.9th, 2021(GMT+8))
- Replace conflux.exe with the new one in Conflux v2.0.0-testnet, then restart the fullnode. Download link: https://github.com/Conflux-Chain/conflux-rust/releases
- The PoS registration will start at Block Number 68845000 (around Dec.9th at 10:00). Reference: PoS Registration Tutorial
- The PoS registration will close at Block Number 69245000 (around Dec.11 at 18:00). After registration closes, you can start adding pos_config. Reference: PoS Transition Tutorial
- The deadline for adding pos_config is before Epoch Number reaches 55665000 (around Dec.13th 15:00). Hardfork upgrade will be completed at this time.
If you upgrade your node after Epoch Number reaches 55095000 or Block Number reaches 68845000 (around 10:00 Dec.9th, 2021(GMT+8)), you need to delete your data, add pos_config, and restart your node. Referenceļ¼Conflux v2.0.0-testnet Test Tutorial
If you start your new node after Epoch Number reaches 55095000 or Block Number reaches 68845000 (around 10:00 Dec.9th, 2021(GMT+8)), you can download the new version Conflux v2.0.0-testnet, add pos_config, and start the node. Referenceļ¼Conflux v2.0.0-testnet Test Tutorial