# Request for information about disputes #GDR-30 **URL:** \ **Category:** Arbitration\ **Created:** [March 27, 2025, 4:55pm UTC](https://forum.thegraph.com/t/request-for-information-about-disputes-gdr-30/6485 "2025-03-27T16:55:26Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![tmigone](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.thegraph.com/tmigone/32/1398_2.png) [@tmigone](https://forum.thegraph.com/u/tmigone)\ **Post date:** [March 27, 2025, 4:55pm UTC](https://forum.thegraph.com/t/request-for-information-about-disputes-gdr-30/6485/1 "2025-03-27T16:55:26Z")
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](https://github.com/graphprotocol/graph-improvement-proposals/blob/main/gips/0009-arbitration-charter.md). * * * Please use this forum for all communications. Arbitration Team. ---
**Author:** ![tonymontana](https://avatars.discourse-cdn.com/v4/letter/t/6f9a4e/32.png) [@tonymontana](https://forum.thegraph.com/u/tonymontana)\ **Post date:** [March 29, 2025, 2:39pm UTC](https://forum.thegraph.com/t/request-for-information-about-disputes-gdr-30/6485/2 "2025-03-29T14:39:20Z")
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`. ---
**Author:** ![tmigone](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.thegraph.com/tmigone/32/1398_2.png) [@tmigone](https://forum.thegraph.com/u/tmigone)\ **Post date:** [April 3, 2025, 11:57am UTC](https://forum.thegraph.com/t/request-for-information-about-disputes-gdr-30/6485/3 "2025-04-03T11:57:57Z")
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. ---
**Author:** ![tonymontana](https://avatars.discourse-cdn.com/v4/letter/t/6f9a4e/32.png) [@tonymontana](https://forum.thegraph.com/u/tonymontana)\ **Post date:** [April 12, 2025, 12:29pm UTC](https://forum.thegraph.com/t/request-for-information-about-disputes-gdr-30/6485/4 "2025-04-12T12:29:35Z")
@tmigone ​It’s been over two weeks without any counterarguments from `0x59749d1fa9635cd0413aeff5ee295490a7e87f54`. Can we proceed with resolving the dispute and processing the transaction? ---
**Author:** ![absolutelyNot](https://avatars.discourse-cdn.com/v4/letter/a/5f8ce5/32.png) [@absolutelyNot](https://forum.thegraph.com/u/absolutelyNot)\ **Post date:** [April 16, 2025, 6:14pm UTC](https://forum.thegraph.com/t/request-for-information-about-disputes-gdr-30/6485/5 "2025-04-16T18:14:51Z")
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. ---
**Author:** ![tmigone](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.thegraph.com/tmigone/32/1398_2.png) [@tmigone](https://forum.thegraph.com/u/tmigone)\ **Post date:** [April 17, 2025, 12:48pm UTC](https://forum.thegraph.com/t/request-for-information-about-disputes-gdr-30/6485/6 "2025-04-17T12:48:48Z")
Dispute resolved at: [Arbitrum Transaction Hash: 0xcac4cacf50... | Arbitrum One](https://arbiscan.io/tx/0xcac4cacf5061f191d6aca9181b61c7cc9f1112c771dea677e93d1b795a0f0e15)