Sixteen-Hour Days and a Promise to Address Phishing

The sale had reached its fourth day. Key buyers, people preparing to run nodes, and users caught in the phishing attack were all waiting for answers. Repeated questions about purchasing and software could no longer be handled through improvised replies in chat.

The founder posted a message that read less like a routine announcement than an admission: “To be honest and transparent,” sales had far exceeded expectations. The team was expanding support, patching the node software, and filling gaps in its documentation and knowledge base. Team members were working more than 16 hours at a stretch; the founder asked the community for patience and said they would grow together. The same message addressed victims of this round of phishing: the team intended to do something for them, though the plan was still being worked out and an answer would come in a few days. The founder said the affected users would be satisfied, thanked everyone for their unwavering trust in $xai, and repeated, “Without the community, we are nothing.”

The narrator remembered the warning four days earlier: no purchase link had yet been published, supposed official links sent by private message were scams, and the team would not cover losses from them. Now the team was speaking of a remedy. The earlier statement set a limit on liability; the new one put pressure on the team to respond to victims. Both belonged in the record. Whether support could catch up, when patches and guidance would be ready, and what victims would receive still depended on concrete plans to come.