The Arbitrators are contacting Indexer address 0xeeeee689aa442c607105f29f06d00d2f748776b2 and fisherman 0xbace05744f1d075ba6bb82ebf561c1c3915f5cd3 for a new dispute filed in the protocol.
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.
Just wanted to share what’s been happening with my GRT node—turns out I’ve been getting slashed nonstop, and I only noticed it yesterday.
Over 4 months, that’s 10 slashes total, costing me 400k GRT. First off, I’ll own up: this is on me. I didn’t fully understand The Graph’s rules, so I accidentally broke them, and that’s why the slashing kept happening. That said, syncing subgraphs here has been brutal. No tools to check subgraph quality beforehand, updates drop out of nowhere, and every time a new version’s indexing hits 90%, it freezes—total nightmare.
And to those “hunters” watching me fall into this trap without a single heads-up? Keep your chips and stay out of my way for good.
I have shut down my node. I’ve made up my mind to leave this community.
Hope you all have a good time here.
Like blowing out your own candle, then complaining it’s too dark for anyone to notice you.
@juanmardefago Do we still need to wait even though the indexer already responded? Considering their behavior, I’m not sure if it makes sense to keep waiting.
Thank you for sharing your perspective and providing additional context. We appreciate the honesty in your post and the effort to explain what happened.
Unfortunately, the behavior reported in this dispute is still an infringement under the Arbitration Charter so the dispute will therefore be accepted. However, this case highlights an opportunity to improve clarity around communication expectations and how support is provided to indexers.
Proposed resolution 1. Accept the dispute.
This case represents a clear breach of the Arbitration Charter and will be processed as such.
2. Clarify documentation.
We’ll update the documentation (e.g., Home | Docs | The Graph and relevant indexer guides) to make it more explicit that while disputes are filed on-chain, communication is expected to take place via the forum. Note that this is already stated in the Arbitration Charter, we will just make it more visible in other mediums.
3. Improve communication reach.
We’ll open a dedicated thread to start a discussion with the indexer community about the “communication problem” — how to make contacting disputed indexers easier. One idea we’d like to propose is including a forum username in the indexer registration data. We’d like to hear from indexers on whether this should be optional, mandatory, or if there are better alternatives.
4. A note on tooling and support.
Some of the challenges you mentioned around tooling or indexing performance are real and can certainly be frustrating, there are existing support channels where these issues can be raised, such as the official Discord, forum threads, or technical support discussions over GitHub. Indexer community and core developers can help address them constructively over those channels.
Once again we appreciate you coming forward. We’ll post the tx hash once it’s executed.
Would it make sense to develop a new indexer mentor program?
It could help newer indexers connect with experienced ones and have a clear contact if issues come up.
Maybe we could host a monthly check-in with a few volunteer OG indexers or Graph staff — just to see how things are progressing and identify any pain points early on. Even if it only ran for six months, it could really help smooth out challenges before they grow.
With Horizon coming online and more data services rolling out, something like this could make onboarding and operations much easier for everyone.