Request for Information about Disputes #GDR-37

The Arbitrators are contacting Indexer address 0x59749d1fa9635cd0413aeff5ee295490a7e87f54 and fisherman 0xfe56931ed1cd3021ef1162bae2b3872e8694d1da for a new dispute filed in the protocol.

Dispute ID: 0x5905e3835f013b756a9503d794449c2cb7a7f4734b5666bc88020c59734a3397

Allocation: 0xa2b81b802e929a17c34d7dc89cb0f1e10cf96284

Subgraph: QmSjdDgdkBewSnVjxkHj4c6H2RMX62utKXebBn3wwaJK7z

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.

Hi @tmigone, it’s me again 0xfe56931ed1cd3021ef1162bae2b3872e8694d1da,
This dispute is similar to as GDR-32, closing a different subgraph which is QmSjdDgdkBewSnVjxkHj4c6H2RMX62utKXebBn3wwaJK7z that was not 100% synced. As of the last check the indexer is still syncing the grafted subgraph QmfKmZ7xfT9PRydVGJRRWEdr7rbBcRoKbDyX7fGK7MCq5j

It is also worth noting that 0x59749d1fa9635cd0413aeff5ee295490a7e87f54 indexer’s endpoint is unreachable now.

Furthermore, this subgraph has been reported to have issues by Ellipfra team here: Discord
There is no history of this subgraph being fully synced except Upgrade indexer. No other indexer has successfully closed this subgraph with a healthy and unique POI except for 0x59749d1fa9635cd0413aeff5ee295490a7e87f54 who submitted twice before.

@tmigone @absolutelyNot ​It’s been a week 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 and precedent set by previous offenses from the same indexer.

We’ll be posting the transaction shortly.

Thanks, Arbitration Team.