Back to collectionStaking V2 sets an upgrade deadline and a pause on deposits
Background: As Staking V2 approached, the Night Watchman and other node operators had to watch their software versions and plan around existing stakes. Today: The team required node software to be upgraded to 1.1.5; once V2 launched, version 1.1.4 and earlier would stop working. Impact and next steps: The Night Watchman reminded the group about the order of upgrading and adding to a stake.
A creative chronicle combining project history with imagined scenes. Story events are not verification of network activity.
Background: As Staking V2 approached, the Night Watchman and other node operators had to watch their software versions and plan around existing stakes. The recurring question of when to upgrade had become a schedule that affected the order of their actions.
Today: The team required node software to be upgraded to 1.1.5; once V2 launched, version 1.1.4 and earlier would stop working. From the upgrade until the V2 release, no one could add to a stake, while existing stakes would keep accruing interest. The new version also added batch submission and batch claiming, saving holders of multiple keys some fees. On the same day, Dolomite launched XAI lending, giving token holders another option to assess for themselves.
Impact and next steps: The Night Watchman reminded the group about the order of upgrading and adding to a stake. He planned to check his own version and existing stake so he would not attempt an operation during the pause. Batch features promised lower costs for multi-key operators, though their ease of use remained to be seen. The new Dolomite option did not answer the operational questions about Staking V2.