Back to collectionA pool restart brings a holder-reported recovery
Responding to raflec's earlier reward question, TokyoLiving said his own rewards had stopped a few days before and identified his pool as XaiBhais. Dhruv suggested another pool if the current one was not operating properly. TokyoLiving then reported contacting the pool team through Telegram: the team restarted the node and, in his words, everything seemed to be working again. Dhruv acknowledged that update.
Responding to raflec's earlier reward question, TokyoLiving said his own rewards had stopped a few days before and identified his pool as XaiBhais. Dhruv suggested another pool if the current one was not operating properly. TokyoLiving then reported contacting the pool team through Telegram: the team restarted the node and, in his words, everything seemed to be working again. Dhruv acknowledged that update.
The useful development was the reported restoration of a particular pool operation, not another generic instruction to claim rewards. TokyoLiving did not say he had switched pools, and his update did not reconcile missed payments or establish the status of raflec's account. The incident nevertheless shows why pool uptime belongs in reward analysis: a local service interruption and the token's redemption mechanism are different sources of risk.