Nimiq Proof of Stake Migration Starts Now for Validator Operators!

This post specifically addresses validator operators participating in the PoS migration. For general information on the migration, see this post: What You Need to Know About Nimiq's Migration to Proof of Stake.

You can find the full documentation here. Below is a short summary of the next steps for validator operators.

Steps for Validator Operators

Main Prerequisite:

Validator Registration: Your validator needs to be registered and appear on this list.

1. Join the Validator Operator's Chat

Join Nimiq’s Discord or Telegram. Reach out to a Moderator/Team Member to verify yourself as a validator operator.

2. Install the Latest PoW Release, now version 1.6.4, which was released on November 13, 2024.

Download the code here or access compiled binaries here.
Syncing Shortcut: Download a snapshot via IPFS or Torrent, extract it, and place it in your PoW client directory to speed up sync time. If using a third-party source, verify it with this SHA256 hash:

97fba2d6a9c8eaeb5fe568337e8052097fdffaae3f047b2f283e7007f30851cf pow-main-full-consensus.zip

3. Download the Latest PoS Release, now 1.0.0-rc.5, which was released on November 17, 2024.

Download it here.

4. Verify your Configuration

Configure client.toml with your validator data as explained in Step 1 of the Activation Guide.
Verify that the seed list matches the list provided in the client.example.toml. The same list is provided below for confirmation:

seed_nodes = [

{ address = "/dns4/aurora.seed.nimiq.com/tcp/443/wss" },

{ address = "/dns4/catalyst.seed.nimiq.network/tcp/443/wss" },

{ address = "/dns4/cipher.seed.nimiq-network.com/tcp/443/wss" },

{ address = "/dns4/eclipse.seed.nimiq.cloud/tcp/443/wss" },

{ address = "/dns4/lumina.seed.nimiq.systems/tcp/443/wss" },

{ address = "/dns4/nebula.seed.nimiq.com/tcp/443/wss" },

{ address = "/dns4/nexus.seed.nimiq.network/tcp/443/wss" },

{ address = "/dns4/polaris.seed.nimiq-network.com/tcp/443/wss" },

{ address = "/dns4/photon.seed.nimiq.cloud/tcp/443/wss" },

{ address = "/dns4/pulsar.seed.nimiq.systems/tcp/443/wss" },

{ address = "/dns4/quasar.seed.nimiq.com/tcp/443/wss" },

{ address = "/dns4/solstice.seed.nimiq.network/tcp/443/wss" },

{ address = "/dns4/vortex.seed.nimiq.cloud/tcp/443/wss" },

{ address = "/dns4/zenith.seed.nimiq.systems/tcp/443/wss" },

]

Verify the network configuration entry is set to main-albatross as provided in the client.example.toml. The final configuration should be the same one as below

network = "main-albatross"

5. Compile the PoS Client

Compile the PoS client as explained in Step 4 of the Activation Guide.

6. Run the Activation Tool

The activation tool will stay active until the end of the migration. It will signal “online” starting approximately 3 days before the candidate block at Proof of Work block #3’456’000.
Once your validator “online” signal has been sent, it will appear as ONLINE on the Migration Readiness Monitor.
When the Activation Phase opens and your validator produces a Genesis Hash, it will appear as READY on the Migration Readiness Monitor.
When more than 80% of the total stake has signaled readiness with the same Genesis Hash, the PoS chain will go live, and validators will begin producing blocks.

Remember to start this process as early as possible to ensure a smooth migration to Proof of Stake. Your dedication and support are invaluable in making this transition a success. Thank you for being an essential part of this journey. See you on the Proof of Stake Network!

Pura Vida
Team Nimiq

Disclaimer

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.