Reward incident traces claim failures to the indexing layer

A developer update relayed by Diablo attributed failed reward claims to a subgraph bug introduced alongside the Referee upgrade for time-based rewards. Operators could not obtain the available claims from challenges, even though they continued submitting assertions. The team said network support had continued and rewards were not lost; after the subgraph fix, restarting an operator would trigger retrieval and claiming of outstanding rewards. This is the team's incident explanation and recovery instruction, not an independently reconciled payout ledger.

For an income-producing node, this incident exposes the distance between doing network work, discovering a claim and receiving a payment. An indexing dependency can interrupt cash-flow visibility and collection without stopping the underlying assertions. A complete recovery assessment therefore compares continuing node work with outstanding claims and settled transfers. Neither an intact activity counter nor the disappearance of an interface error alone closes that reconciliation.