Back to collectionA December Deadline for Sentry Nodes
The argument about partner games was still unsettled when node operators received a task with a firm deadline. An official notice said data indexer Alchemy was shutting down its subgraph service, so Sentry nodes had to move to GoldSky. The upgrade turned an infrastructure change into a deadline for every node operator.
A creative chronicle combining project history with imagined scenes. Story events are not verification of network activity.
The argument about partner games was still unsettled when node operators received a task with a firm deadline. The Night Watchman had maintained Sentry nodes for a long time. He first needed to make sure his own machines would keep working, then explain the update clearly enough for other operators to follow.
An official notice said data indexer Alchemy was shutting down its subgraph service, so Sentry nodes had to move to GoldSky. Both desktop and command-line clients needed version 2.2.0; older versions would stop working if they were not updated before December 8. That evening, the Night Watchman updated all three of his machines and rewrote the command-line procedure as steps for the community, so operators using a terminal would not miss it.
The upgrade turned an infrastructure change into a deadline for every node operator. The Night Watchman's three machines were updated, and his post gave others a place to start. He would watch for steps where people got stuck, but whether other nodes met the December 8 deadline depended on their operators completing the update.