I am disputing indexer 0xf6a9bad58e74b5165dc31ef24be4377b192f274a for repeatedly closing the subgraph ENS (QmYrEJKHphWBGkqPkEVKSZR9gsoD6RtJs3g3R8iWVhH66Z) with the same POI (0xdf1d1d2a861bbc890ddac6650d500394a763ce87885bcf9f56550721aca0e47b) over a period of months, as related to the first dispute ID (0xa49bf1f80f58a67c6627d783a45190d25a56cfff3d6a76e98994262baeb2c07c).
The first occurrence was on May 21, 2024, with the allocation ID (0x9c75628171726a9ee18f438d4e7f99bf586042eb). This allocation was initially closed with the POI (0xdf1d1d2a861bbc890ddac6650d500394a763ce87885bcf9f56550721aca0e47b). Subsequently, it was closed multiple times with the same POI, up until the most recent allocation.
For the second dispute ID (0xd3a3856ecd8d203a27c39e9f352ce96dbc82cf1caa0a930ba2a4e5ce8727734c), they closed the allocation ID (0xbc0ec2024d8ec731c9ec2ea9c3b304b424da0961) with a different POI (0xef31e8ea7ad1e53f467bddbb0ecf04bc7372486612d3603551aac2f18ab27daa). Upon checking the explorer, the explorer showed a sync status failure for the disputed indexer and was about 17 million blocks behind on this subgraph.
Further checks using the Query Cross-Checking Tool to capture their public POI show that this indexer’s POI differs from the majority of other indexers on this subgraph. Attached below are screenshots of query checks for start blocks #20878337, #21043937, and #latest all respectively to the closed epoch. All screenshots confirm the same public POI for the disputed indexer.
An extra context on this subgraph: it requires additional steps to avoid an error:
“failed to process trigger: block #3330220 (0x4ea8…4748), transaction 057a18943891fc4defd54ff6b18c4fa1e15b822f299f2f08117e4fd11d44f971: error while executing at wasm backtrace:\t0: 0x4770 - !src/ensRegistry/_handleNewOwner\t1: 0x4de2 - !src/ensRegistry/handleNewOwnerOldRegistry: Missing ENS data: see GitHub - graphprotocol/ens-rainbow”
The extra steps are defined in ENS Rainbow GitHub.
Furthermore, the subgraph will return this NON-DETERMINISTIC ERROR:
ERRO Subgraph failed with non-deterministic error: failed to process trigger: block #3330220 (0x4ea8…4748), transaction 057a18943891fc4defd54ff6b18c4fa1e15b822f299f2f08117e4fd11d44f971: error while executing at wasm backtrace: 0: 0x4770 - !src/ensRegistry/_handleNewOwner 1: 0x4de2 - !src/ensRegistry/handleNewOwnerOldRegistry: Missing ENS data: see GitHub - graphprotocol/ens-rainbow, retry_delay_s: 231, attempt: 1, sgd: 127, subgraph_id: QmYrEJKHphWBGkqPkEVKSZR9gsoD6RtJs3g3R8iWVhH66Z, component: SubgraphInstanceManager
Therefore, there is no reason for the disputed indexer to close this subgraph multiple times with an obviously invalid POI. Out of 16 indexers on this subgraph, 15 are fully synced, with this disputed indexer as the only exception.
Finally, it’s worth noting that this indexer allocates solely to this particular subgraph, with a 100% reward cut and fee cut. As a result, the current APR for this indexer consistently shows 0%, likely to be inconspicuous.