logologo
expand button
APP
Bridge icon
Bridge
eSpace Airdrop icon
eSpace Airdrop
Governance icon
Governance
Web3 Paywall icon
Web3 Paywall
Advanced
Pos icon
Pos
Risk warning
Notice 1
Some operations may cause your pending staking token to be permanently locked, including but not limited to:
1. Modify the codes of Conflux-rust, resulting in a certain kind of consensus-breaking behavior in your PoS account.
2. 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.)
3. The theft of the PoS private key which causes the above phenomenon.
4. The PoW address private key bound to the PoS private key is lost, failing to issue the unlocking instruction.\nNote: 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 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 rewards, including but not limited to:
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:
1. 7 days after sending the unlocking instruction
2. 14 days after locking the token is locked in multiple batches, the unlocking time of each batch shall be calculated separately.
PoS mining steps
You need to upgrade your node before Epoch Number reaches 36935000 or Block Number reaches 92060600 (around 12:00 Feb.23rd, 2022(GMT+8))
1. Replace conflux.exe with the new one in Conflux v2.0.0, then restart the fullnode. Download link: https://github.com/Conflux-Chain/conflux-rust/releases
2. The PoS registration will start at Epoch Number 36935000 or Block Number 92060600 (around Feb.23rd at 12:00, 2022). Reference, PoS Registration Tutorial:https://forum.conflux.fun/t/pos-registration-tutorial-conflux-v2-0-0/13469
3. The PoS registration will close at Block Number 92406200 (around Feb.25th at 12:00, 2022). After registration closes, you can start adding pos_config. Reference, PoS Transition Tutorial: https://forum.conflux.fun/t/pos-transition-tutorial-conflux-v2-0-0/13470
4. The deadline for adding pos_config is before Epoch Number reaches 37230000 (around Feb.28th 12:00, 2022). Hardfork upgrade will be completed at this time.