（will be updated…）
This website is the Beta Version of Conflux Governance, and the link network is the Conflux PoS testnet (version: conflux_v1.2.0-rc-1). The data is used for the 3rd round public test of the Conflux PoS testnet. This network is only for test use. 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 codes 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 theft of the PoS private key which causes the above phenomenon.
- The PoW address private key bound to the PoS private key is lost, failing to issue the unlocking instruction.
Note: If the PoS private key is lost but not stolen, it will not cause capital loss. Use the PoW address to send the unlocking instruction.
Notice 2: Some operations may cause your staking token to automatically enter the unlocking state, including but not limited to:
- After being selected into the PoS Committee, fail to bear the responsibility of a committee member to vote for the PoS block for over an epoch (about one hour) due to the program running stop, network failure, malicious attack, or other reasons.
Note: In this case, when all staking is completely unlocked, the PoS address will return to normal use.
Notice 3: Some operations may result in you not getting any interest, including but not limited to:
- Fail to successfully run the PoS node and 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 of the private key address shall be fully responsible for the security of funds.
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:
- 9 hours after sending the unlocking instruction;
- Having been locked for 18 hours.
If the token is locked in multiple batches, the unlocking time of each batch shall be calculated separately.