# Request for information about disputes #GDR-28

**URL:** <https://forum.thegraph.com/t/request-for-information-about-disputes-gdr-28/6402>\
**Category:** Arbitration\
**Created:** [February 11, 2025, 5:25pm UTC](https://forum.thegraph.com/t/request-for-information-about-disputes-gdr-28/6402 "2025-02-11T17:25:54Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![absolutelyNot](https://avatars.discourse-cdn.com/v4/letter/a/5f8ce5/32.png) [@absolutelyNot](https://forum.thegraph.com/u/absolutelyNot)\
**Post date:** [February 11, 2025, 5:25pm UTC](https://forum.thegraph.com/t/request-for-information-about-disputes-gdr-28/6402/1 "2025-02-11T17:25:54Z")

</div>

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

```auto

DisputeID: 0xe1eb801fee6d7c849273d7c3a75998ef004c62b1ed092ec3927bee9fb9ce1929

Allocation: 0xc47a4ca51c5a59b9dd4466b9872f0063e1042e2e

Subgraph: QmUbSegbKWhJ4N98iRjfEpMiogGLF2cN77Uqqbd5NKm6g7

```

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.

---

<div class="post-metadata">

**Author:** ![tonymontana](https://avatars.discourse-cdn.com/v4/letter/t/6f9a4e/32.png) [@tonymontana](https://forum.thegraph.com/u/tonymontana)\
**Post date:** [February 11, 2025, 7:48pm UTC](https://forum.thegraph.com/t/request-for-information-about-disputes-gdr-28/6402/2 "2025-02-11T19:48:17Z")

</div>

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

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

Please check [https://indexer.gunu-node.com/status](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.

---

<div class="post-metadata">

**Author:** ![absolutelyNot](https://avatars.discourse-cdn.com/v4/letter/a/5f8ce5/32.png) [@absolutelyNot](https://forum.thegraph.com/u/absolutelyNot)\
**Post date:** [February 24, 2025, 4:45pm UTC](https://forum.thegraph.com/t/request-for-information-about-disputes-gdr-28/6402/3 "2025-02-24T16:45:43Z")

</div>

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. It is worth noting that the indexer’s endpoint is now offline and cannot be reached for historical POI data.

---

<div class="post-metadata">

**Author:** ![Felix1](https://avatars.discourse-cdn.com/v4/letter/f/3e96dc/32.png) [@Felix1](https://forum.thegraph.com/u/Felix1)\
**Post date:** [February 24, 2025, 7:05pm UTC](https://forum.thegraph.com/t/request-for-information-about-disputes-gdr-28/6402/4 "2025-02-24T19:05:24Z")

</div>

Yes i like to file dispute and im the fool

---

<div class="post-metadata">

**Author:** ![tonymontana](https://avatars.discourse-cdn.com/v4/letter/t/6f9a4e/32.png) [@tonymontana](https://forum.thegraph.com/u/tonymontana)\
**Post date:** [February 25, 2025, 12:50pm UTC](https://forum.thegraph.com/t/request-for-information-about-disputes-gdr-28/6402/5 "2025-02-25T12:50:38Z")

</div>

The indexer’s endpoint is up and fully operational. It is queryable, and the explorer shows the indexing progress for all three subgraphs.

---

<div class="post-metadata">

**Author:** ![tonymontana](https://avatars.discourse-cdn.com/v4/letter/t/6f9a4e/32.png) [@tonymontana](https://forum.thegraph.com/u/tonymontana)\
**Post date:** [March 4, 2025, 2:44pm UTC](https://forum.thegraph.com/t/request-for-information-about-disputes-gdr-28/6402/6 "2025-03-04T14:44:31Z")

</div>

@absolutelyNot just checking in—any updates on the three disputes?

---

<div class="post-metadata">

**Author:** ![tonymontana](https://avatars.discourse-cdn.com/v4/letter/t/6f9a4e/32.png) [@tonymontana](https://forum.thegraph.com/u/tonymontana)\
**Post date:** [March 6, 2025, 2:14pm UTC](https://forum.thegraph.com/t/request-for-information-about-disputes-gdr-28/6402/7 "2025-03-06T14:14:50Z")

</div>

Dear @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.

---

<div class="post-metadata">

**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 6, 2025, 8:02pm UTC](https://forum.thegraph.com/t/request-for-information-about-disputes-gdr-28/6402/8 "2025-03-06T20:02:18Z")

</div>

@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.

We will shortly initiate the transaction to resolve this dispute. Thanks, Arbitration Team.

---

<div class="post-metadata">

**Author:** ![tonymontana](https://avatars.discourse-cdn.com/v4/letter/t/6f9a4e/32.png) [@tonymontana](https://forum.thegraph.com/u/tonymontana)\
**Post date:** [March 10, 2025, 6:46pm UTC](https://forum.thegraph.com/t/request-for-information-about-disputes-gdr-28/6402/9 "2025-03-10T18:46:34Z")

</div>

@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.

---

<div class="post-metadata">

**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 11, 2025, 3:08pm UTC](https://forum.thegraph.com/t/request-for-information-about-disputes-gdr-28/6402/10 "2025-03-11T15:08:59Z")

</div>

Transaction has been executed now: [Arbitrum One Transaction Hash (Txhash) Details | Arbitrum One](https://arbiscan.io/tx/0xe1051e32d1b22441bf5648a9907fe64f02da67b128d92a64f5cd09205160cb1a)

Thanks, Arbitration team.
