Request for information about disputes #GDR-26

Governance & GIPs Arbitration
1

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

DisputeID: 0xb58dbe83901a6cd6962783d179737a8fe7025d8a1872579fe32a446abb029767

Allocation: 0xffa41b698da14c514314f5b576460abc0575a3b9

Subgraph: Qme9hQY1NZ8ReVDSSQb893s2fGpeLkgfwXd3YU5rndACaP

Fisherman (0xfe56931ed1cd3021ef1162bae2b3872e8694d1da), could you share the 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
2

Hi @absolutelyNot, I’m 0xfe56931ed1cd3021ef1162bae2b3872e8694d1da, the one who submitted this dispute.

This dispute concerns the indexer closing Qme9hQY1NZ8ReVDSSQb893s2fGpeLkgfwXd3YU5rndACaP subgraph that was not 100% synced.

Please check https://indexer.gunu-node.com/status on the indexer’s publicProofsOfIndexing. The subgraph was closed on epoch 801 on the Gnosis chain. By checking the ebo, the block number for eip155:100 would be 38436099.

After checking it returned "message":"Null value resolved for non-null field proofOfIndexing", the explorer also shows that it is not synced.

3

The Arbitration team has resolved to accept the dispute by end of week unless the indexer 0x59749d1fa9635cd0413aeff5ee295490a7e87f54 clarifies the reported behavior and provides a reasonable explanation for the POI discrepancy.

Worth noting that the indexer’s endpoint is now offline and cannot be reached for historical POI data.

4

To @tmigone @absolutelyNot,

I don’t want to sound rude, but it’s been more three weeks without any follow-ups. As mentioned, it was supposed to be completed by the end of last week if there were no counter arguments from 0x59749d1fa9635cd0413aeff5ee295490a7e87f54. However, it seems the matter is still ongoing.

5

@tonymontana, apologies for the delay. Given the disputed indexer’s lack of response in this thread we wanted to make sure slashing was the correct decision so we spent a bit more time double checking everything.

Arbitrators have resolved to slash the indexer. The following points are useful context to understand the decision:

  • The indexer closed an allocation with a non zero POI at epoch 801, with indexed chain block number 38436099.
  • The indexer’s public endpoint shows that they are currently indexing the subgraph but are not fully synced and block 38436099 is not yet indexed. After monitoring the status in the past days/weeks there’s seems to be little progress if any towards getting the subgraph fully synced.
  • In an effort to validate the POI against another source, the POI presented by the indexer at epoch 801 has been tested against the calculated POI for this same indexer using the graph-node database from the Upgrade Indexer. The resulting calculated POI does not match the presented POI. Note that this does not mean that the disputed indexer’s POI is invalid as the Upgrade Indexer is not to be considered the source of truth for POIs, but it does mean that one of the POIs must be invalid.
  • After three weeks the disputed indexer has not reached out to provide a counter argument that can explain this behavior.

Once we initiate the transaction we will post the details here. Thanks, Arbitration Team.

6

@tmigone Is the arbitration team going to process the transaction already, or do I have to wait another week? I don’t understand why this is taking so long, especially when the investigations have already been clearly completed.

7

Transaction has been executed now: Arbitrum One Transaction Hash (Txhash) Details | Arbitrum One

Thanks, Arbitration team.