Back to collectionTwo Required Node Updates, Staking Still Weeks Away
After challengers and Sentry nodes moved to mainnet, operators had to watch both node activity and multiple keys. Overnight, node software received two required updates. The Night Watchman could finally check his keys and last challenge time in one place.
A creative chronicle combining project history with imagined scenes. Story events are not verification of network activity.
After challengers and Sentry nodes moved to mainnet, operators had to watch both node activity and multiple keys. Staking still had not opened, and questions about it kept coming. The Night Watchman wanted to see which immediate problems a software update could actually solve.
Overnight, node software received two required updates. Version 1.0.82 added public-node access, a dashboard showing the status of all an operator’s keys, and the time of the most recent challenge. Two hours later, version 1.0.83 fixed several minor interface problems. Asked again when staking would be available, support still said, “A few more weeks.”
The Night Watchman could finally check his keys and last challenge time in one place. He planned to compare the new dashboard with his daily notes, then ask about any status he could not interpret. The interface had improved, but the staking wait had not shortened; “a few weeks” was still no firm date.