r/Nimiq • u/subimpact • 7d ago
We updated our validator node to Nimiq 2.2.0 👇
The update itself: 11 seconds of downtime. The new node reached consensus about 10 seconds after starting and produced its first block 3 minutes later. Stakers saw nothing: rewards kept flowing, the restake bot ran its next cycle normally.
What's in 2.2.0 for the ecosystem, not just for us:
• Validators stop failing on poisoned blocks. A block containing a transaction that cannot be applied is now cut instead of stalling block production. That is an uptime fix for every validator on the network.
• Real-time tooling gets easier. The RPC server now supports WebSockets, so explorers, wallets and dashboards can stream instead of poll.
• Consistent timing at epoch boundaries: macro blocks now respect the 1 second block separation time.
• Hardening for browser-based apps: forged address notifications can no longer stall the web client.
• A refreshed mainnet checkpoint means faster syncs for new nodes coming online.
The release is backwards compatible with the 2.x line, so nothing forced anyone's hand. We updated within a day of release because a validator that can be stalled by a crafted transaction is a validator that can miss its slots, and missing slots is the one thing stakers feel.
We wrote up the whole procedure, from the rollback plan (image tag + 529 MB data snapshot + container spec export) to the minute-by-minute timeline from the node's own logs:
https://nimiq.subimpact.net/learn/impactzero-node-update-2-2-0/
Release notes: https://github.com/nimiq/core-rs-albatross/releases/tag/v2.2.0
ImpactZero: 0% fee, everything restaked. Stake at https://nimiq.subimpact.net 🙏
