Request for Information about Disputes #GDR-38

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

Dispute ID: 0xf58ff3abd02b90a25fb0356bc9366cc60eeb47bf0b2dc9b885b126fa6290edfb

Allocation: 0xe16be3fd3afe86e7df1f042bc3e81bd6403eae1d

Subgraph: QmQEYSGSD8t7jTw4gS2dwC4DLvyZceR9fYQ432Ff1hZpCp

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.

Cheers arbitrators.

This one’s about Protofire with the use of manual POI on Quickswap subgraph that doesn’t line up with the closed epoch which they used the latest POI from their synced block instead, as mentioned in Discord.

There are quite a few indexers synced to chainhead, so the subgraph looks healthy from our side. Unless Protofire can show it’s actually a deterministic issue and not just something on their end, it seems off.