Hi @AxiomaticAardvark and arbitrators,
We’ve reproduced it and agree with the finding.
**What we confirmed**
- Our response to the disputed query hashes to the attested `responseCID`, so it is the answer our nodes served, and they still return it.
- Our ftnGO store has no `Filled` entity for tx `0x0f91931d…` (block 21,804,357). Comparing against the contract’s on-chain logs, we’re missing 11 events in total, in three block windows: about 21,088,000–21,093,500 and 21,116,000–21,122,900 (November 2024), and 21,804,300–21,804,600 (February 2025). Events on either side of each window are present.
- governance-v3 has the same problem: `constants` id `100` doesn’t exist in our store. That deployment keeps full history, so pruning isn’t the cause.
- All staked.cloud indexers query the same graph-node store, which is why the three allocations returned identical responses.
**Likely cause**
The gaps look like `eth_getLogs` responses that came back successful but incomplete during the original indexing. graph-node treats a successful response as complete, so it skipped those events without an error. Our current store is a January 2026 copy of the original deployment and inherited the gaps. We no longer have RPC or graph-node logs from that period, so we can’t tell which provider returned the incomplete data.
**What we’ve done**
On October 21 we stopped allocating to both deployments and closed every staked.cloud allocation on them; none remain open. We intended to close them with a zero POI, but our close command omitted `–force`. The agent rejected the zero POI, and the allocations were then closed with the POI graph-node computed from the incomplete store. We didn’t intend to further profit off of incorrect data and we’re going to hold off allocating to these subgraphs until this dispute is resolved and we’ve successfully resynced. We’re correcting our runbook so future zero-POI closes are submitted as intended.
**Questions**
1. Is there any additional information you’d like from us?
2. We’d like to start resyncing both subgraphs. Do you need us to keep the current data for further proof of indexing? If so, would a database dump of both deployments, kept until the dispute is resolved, be enough, or would you prefer we keep the current store live and queryable?
3. Before we allocate again, we plan to verify the resynced data against on-chain logs and other indexers’ POIs. Are there other steps you’d recommend to make sure this doesn’t happen again?
Thanks,
Staked Team
Note this response was generated with some AI help 