With Nimiq’s evolution to Proof-of-Stake now in the DevNet phase, we've begun to integrate staking into the Nimiq Wallet. While many features are still yet to be implemented, we thought it would be nice to share early access with our community to let you get an idea of how Nimiq’s next upgrade will look and feel.
The switching of Nimiq’s protocol to Proof-of-Stake (PoS) is an upgrade long awaited by the Nimiq community. Our blockchain engineers recently published the Nimiq Proof-of-Stake DevNet release-candidate and shared RPC access to interested devs for them to test how it fits their use cases. We've continued to fine-tune and test the DevNet and, with current RPC access ready to go, the next natural step was to begin integration of DevNet staking into the Nimiq Wallet.
Today, we're very happy to present the first DevNet-version of Nimiq with Proof-of-Stake in the Nimiq Wallet.
As we're getting to the point where this upgrade is beginning to be tested not only by developers but also by non-technical users, we'd like to take this opportunity to state that going forward we are looking to talk about the Proof-of-Stake or “Albatross” upgrade that is happening to Nimiq rather than referring to Nimiq 2.0. Similar to Bitcoin not having version numbers, Nimiq remains Nimiq (and NIM remains NIM) as proposed upgrades in the underlying software are adopted by the Nimiq community.
The Nimiq Developer Network, or DevNet for short, is a laboratory for all Nimiq developers to experiment and test out the new Nimiq Proof-of-Stake protocol. Since it's set up as a testing environment, the DevNet is subject to resets, with everything that that entails (staking rewards lost, accounts no longer holding funds, etc). The current Nimiq Mainnet and the Nimiq DevNet are completely separate networks and are not compatible with each other. Please make sure not to send real NIM or to use your actual Nimiq account in the DevNet. If you want to test the DevNet, always create a fresh account - and keep in mind that it does not work within any app in the Nimiq Ecosystem.
With the progress that we've made, we felt that this was the perfect time to share early access with our community, so that you can get a feel for just how Proof-of-Stake works with the Nimiq Wallet. Having said that, there are some things to keep in mind while trying it out:
The Nimiq Wallet is actually connected to a running network of Proof-of-Stake DevNet nodes currently managed by the Nimiq team. Nothing you see in the DevNet staking Wallet is a simulation. Sending NIM, staking, un-staking and payouts are real (in devNIM). Currently, our focus lies on running the DevNet under regular conditions. Security hardening will follow later. If you find anything that feels like a bug, please share it in the Nimiq Forum.
The Nimiq wallet allows users to delegate their stake to a validator through RPC. Nimiq Proof-of-Stake is non-custodial, so delegating stake to a validator pool does not bear the risk of surrendering the NIM to the pool manager.
We are currently working on enabling community developers to become validators in the DevNet. Since at the moment there's no support for others to create validating pools, the only validating pools available in the Wallet are fictional, just for testing purposes. We do use settings for each pool to showcase the trust score sorting of the Wallet. Because these settings are up to the validator some aspects of the staking experience depend on them. When more external validator pools are added, the different settings and configurations of different validator pools can be tested. Examples of this:
Many variables of the protocol are going to be changed and fine-tuned to find the best setting for Nimiq Proof-of-Stake, which is one of the main intentions of the Nimiq DevNet and the tests we run with the Wallet. For this reason, some aspects of the staking user experience might be different to those that Nimiq Proof-of-Stake will have when it reaches its final stage. Some of these include:
Nimiq Mainnet and Nimiq Proof-of-Stake DevNet (Albatross) run in completely different networks. Although you can send DevNet NIM with your friends to test it out, do not send real NIM to the DevNet wallet because they will be lost forever. DO NOT use your mainnet account in any way. In any case, it doesn't hold any funds in DevNet. Just create a fresh DevNet account for testing these features. A generous faucet provides the NIM necessary.
The interface is a work-in-progress, too. Some parts are still missing, or are subject to change. While the staking feature works and rewards can be seen as your stake grows with each payout, the history of these payouts is not yet implemented. Special validators are available who will not add the rewards to your stake but instead send them to you directly. In case you want to see a hefty transaction history, delegate your stake to “Monopooly" or "Cool pool”.
We'll keep you posted when we add new features and functionalities for you to try, so stay tuned to our official Twitter account to learn more and be amongst the first to test them out!
Thanks for bearing with us and reading all of that important information! You can test out the Nimiq DevNet Wallet here: wallet.v2.nimiq-testnet.com. Plus we prepared a full tutorial which can be found here. We're planning a community event to test the Wallet all together, with cool prizes involved for users that are actively testing it and sharing it with their friends and followers.
Happy DevNet Staking and Pura Vida!
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.