The Arbitrators are contacting Indexer address 0x59749d1fa9635cd0413aeff5ee295490a7e87f54 and fisherman 0xfe56931ed1cd3021ef1162bae2b3872e8694d1da for a new dispute filed in the protocol.
Dispute ID: 0x7b4fd0a2217095ed63251c1b7dbf2f1198b5401d069d903ff5feb9a52ae1334b
Allocation: 0xd47415c285e4015da17e43bd671fb9e8aefd2292
Subgraph: QmWHxCtPAktZnfqnCEgPcuSesv4oDQssjgyzMvCAE4RQqr
Fisherman, could you share the insights or data you gathered that led to you filing the dispute? Please provide all relevant information and records about the open dispute. This will likely include POIs generated for the affected subgraph(s).
About the Procedure
The Arbitration Charter regulates the arbitration process. You can find it in Radicle project ID rad:git:hnrkrhnth6afcc6mnmtokbp4h9575fgrhzbay or at GIP-0009: Arbitration Charter.
Please use this forum for all communications.
Arbitration Team.
1 Like
Hi @tmigone, it’s me again 0xfe56931ed1cd3021ef1162bae2b3872e8694d1da
This dispute is same as GDR-27, closing QmWHxCtPAktZnfqnCEgPcuSesv4oDQssjgyzMvCAE4RQqr subgraph that was not 100% synced. The indexer only synced up to block 36560205, while the correct startBlock should have been 39114673 epoch 841.
1 Like
Hi @tonymontana thanks for the information.
We’ve verified the following:
- Indexer closed allocation with non-zero POI at epoch
841, at indexed chain block height 39114673
- Indexer’s status endpoint reports the subgraph is not synced past block
36560205
Additionally we are in the process of validating the presented POI using other synced up indexers as reference point.
To the disputed indexer 0x59749d1fa9635cd0413aeff5ee295490a7e87f54, is there a reason why this keeps happening? Please share relevant logs for the indexer-agent and graph-node at the time the allocation was closed.
2 Likes
@tmigone It’s been over two weeks without any counterarguments from 0x59749d1fa9635cd0413aeff5ee295490a7e87f54. Can we proceed with resolving the dispute and processing the transaction?
The Arbitration Team has reviewed the evidence related to the recent allocation closed by indexer 0x59749d1fa9635cd0413aeff5ee295490a7e87f54 and is proceeding with a slash based on the findings outlined above. This data suggests the indexer submitted a POI for a subgraph that was not fully synced, which is grounds for slashing. In addition, we have not received a response or data from the Disputed Indexer within 20 days, which aligns with prior precedent.
1 Like