A Compromised Gateway and a December 15 Target
The Odyssey was still running on the testnet. In the afternoon, officials warned that the points platform’s domain had been hijacked: people should stay off the site and sign no transactions. The narrator read the two announcements side by side: one told people to avoid a compromised gateway, while the other asked them to keep stressing the testnet.
A creative chronicle combining project history with imagined scenes. Story events are not verification of network activity.
The Odyssey was still running on the testnet. Community members used the points platform to record daily tasks, while the developers were preparing to put more load on the chain. For the narrator, the day brought two linked problems: securing access first, then explaining how far the event would run.
In the afternoon, officials warned that the points platform’s domain had been hijacked: people should stay off the site and sign no transactions. That stopped the daily claiming routine for most participants. Officials then offered a detour: the minting page still worked directly, so people could mint first and claim their points once the platform recovered. That evening, they announced that the Odyssey would continue until mainnet instead of ending as originally planned; the mainnet date stated at the time was December 15. Sentry nodes were scheduled to reach the testnet in November and expand with mainnet. The aim was to push the chain toward its maximum traffic capacity and check whether Sentries would be dependable when mainnet opened. All 42 Pioneer avatars could be minted again each day to create that load. Sentries would be open to everyone, with full explanations of the nodes and desktop client to follow during October.
The narrator read the two announcements side by side: one told people to avoid a compromised gateway, while the other asked them to keep stressing the testnet. The detour kept minting possible, but points claims and safety checks would have to wait for the platform’s recovery. The longer schedule also left the community watching whether the node and mainnet plans could hold up.