Nimiq Pre-Staking Campaign has concluded, with over 5.7 billion NIM pre-staked by more than 1500 addresses. This blog post outlines the next steps in Nimiq's transition to Proof of Stake.
10 Nov
by
5 min
The Nimiq Pre-Staking Campaign phase has come to an end, marking an exciting milestone on Nimiq’s path to Proof of Stake. Thanks to the overwhelming support of the Nimiq community, the base goal of 2 billion NIM was met in just 48 hours, ensuring a robust migration to Proof of Stake. Since then, the pre-staked amount has grown substantially, with over 5.7 billion NIM pre-staked by more than 1500 addresses. This reflects the strong commitment from the Nimiq community for the migration to Proof of Stake. A huge thank you to everyone who participated!
The focus now shifts to the Activation Phase, scheduled to commence on November 19, 2024, at approximately 8:00 AM UTC, corresponding to block #3’456’000 on the Proof of Work chain.
For users not operating a validator, the migration is expected to be seamless. No action is required on your part unless you are going to operate a validator during the migration. Your NIM will remain safe, and you can continue using your wallet as usual once the migration is complete.
All possible precautions have been taken to ensure completion within an hour after the activation window opens approximately on November 19 at 8:00 am UTC, when block #3’456’000 is mined in PoW. However, as this is a decentralized process (read Start of the PoS Mainnet Chain from the Nimiq Developer Center to learn more), initiated by network validators and supported by community developers globally, there is a chance that not all validators will be ready when the activation window opens. If you're curious about what happens if some validators are not ready in time, please refer to the section below, What to Expect if Multiple Activation Windows Are Needed.
If everything goes as expected, the required validators are ready and the migration process starts as soon as the activation window opens, here’s what to expect:
For those interested in the technical aspects, below is an explanation of what to expect during the Activation Phase.
As soon as the Activation Phase begins at Proof of Work Block #3’456’000, that very block will be used as the candidate transition block, initiating a 24-hour window for the transition to Proof of Stake with that block’s state. Validators who registered during the Validator Registration Phase will be able to signal their readiness to migrate during this period. The transition will only occur once validators representing 80% or more of the total pre-staked NIM signal readiness.
If the readiness threshold is not met within the 24-hour window for unexpected reasons, the activation will reset, and a new candidate transition block will be selected for another activation attempt. Given the strong support from community-managed pools, a successful transition within the first activation window can be anticipated. However, every scenario must be considered, and therefore the protocol is designed to handle multiple attempts if necessary to ensure a secure transition. For those curious about the process in case multiple activation windows are required, continue reading.
Even if validators have issues signaling readiness, the migration process is designed with that possibility in mind. To ensure a smooth transition, validators will signal their online state starting 3 days before the first activation window at block height 3’456’000. Once 80% of the total stake signals readiness, the PoS chain launches. If this threshold isn’t reached in the first window, additional 24-hours windows will open every 1’400 PoW blocks. By the 5th window, validators who have not shown readiness are removed from the count, increasing the likelihood of reaching the 80% threshold. These removed validators will be deactivated for the first epoch of the PoS chain but can resume their active state from the second epoch onwards. This process continues until the 80% is reached.
For more information, visit the Migration Section in the Nimiq Developer Center.
With the Pre-Staking Phase concluded, our attention now turns to ensuring a successful migration to Proof of Stake. After the migration is confirmed, exchanges and third-party wallets are operational, and the new Proof of Stake chain is stable, we will begin distributing Pre-staking rewards and selecting giveaway winners. As stated in the Pre-staking Campaign, this process may take up to three months following the migration. Stay tuned to Nimiq's official channels for updates on pre-staking rewards and giveaways.
Exciting developments are on the horizon! With the transition to Proof of Stake, we will launch initiatives aimed at driving mass adoption of crypto payments and continue to grow the Nimiq community through engaging events. We extend our deepest gratitude to all who have supported us on this journey. The best of Nimiq is yet to come.
See you on the Proof of Stake network!
Pura Vida,
Team Nimiq
None of the statements must be viewed as an endorsement or recommendation for Nimiq, any cryptocurrency, or investment product. Neither the information, nor any opinion contained herein constitutes a solicitation or offer by the creators or participants to buy or sell any securities or other financial instruments or provide any investment advice or service. All statements contained in statements made in Nimiq’s web pages, blogs, social media, press releases, or in any place accessible by the public, and oral statements that may be made by Nimiq or project associates that are not statements of historical fact, constitute “forward-looking statements”. These forward-looking statements involve known and unknown risks, uncertainties, and other factors that may cause the actual future results, performance, or achievements to be materially different from any future results, performance, or achievements expected, expressed, or implied by such forward-looking statements. The final decision of implementing any changes to the Nimiq protocol, including its parameters, always remains with the decentralized node operators who agree what version and parameters to deploy and support.