Request for information about disputes #GDR-6

The arbitrators are contacting indexer address 0x81dd719fd7efb19d12740b8057c0e363bee35b4a (decisionbasis-bestake) about disputes filed in the protocol.

To make the investigation as brief as possible, please provide the following information and any other relevant records about the open disputes:

  • Version of graph-node used.
  • Graph-node configuration in full.
  • Type and version of Ethereum node.
  • Table of PoIs generated by the affected subgraphs.
  • A dump of the call cache data from the database for the affected subgraphs.
  • Entity values as of the divergent block once identified.

This is not an all-inclusive list. Request for additional information may be made if considered necessary.

How to Get Relevant Data

You can use the following queries to extract information from the indexer software to be used in the evaluation.

# Get subgraphs schema
SELECT name FROM public.deployment_schemas where subgraph = 'QmTj6fHgHjuKKm43YL3Sm2hMvMci4AkFzx22Mdo9W3dyn8';

# Move to the subgraphs schema

# Dump PoI TABLE - (from outside of psql console but on server)
pg_dump --dbname="<YOUR_DB_NAME" --host=<DB_HOST> --port=5432 --username=<USERNAME>  --table='<SUBGRAPH_SCHEMA>."poi2$"' --file='<FILE_TO_SAVE_TO>'

# Dump call cache (on some setups this table may be in a different schema, check it with `select * from public.chains`)
pg_dump --dbname="<YOUR_DB_NAME" --host=<DB_HOST> --port=5432 --username=<USERNAME>  --table='public.eth_call_cache"' --file='<FILE_TO_SAVE_TO>'

Once a divergent block is identified:

# loop through all entity tables and get changes for that block
# for each entity table in subgraph deployment schema:
select * from <entity_table> where lower(<DIVERGENT_BLOCK>);

Purpose of the Requirement

This requirement is related to the following disputes:

├─ 0x3cd2fdf99d3d8612c8a1d205c96bb2b7e0cffbf7f95249e0f549a59f071e9543
│  ├─ Type: Indexing
│  ├─ Indexer: 0x81dd719fd7efb19d12740b8057c0e363bee35b4a
│  ├─ Fisherman: 0xb25813a23c3cb8852133416ba6adc30552880dc3
│  ├─ SubgraphDeployment
│  │  └─ id: 0x014e8a3184d5fad198123419a7b54d5f7c9f8a981116462591fbb1a922c39811 (QmNRkaVUwUQAwPwWgdQHYvw53A5gh3CP3giWnWQZdA2BTE)
│  ├─ Allocation
│  │  ├─ id: 0xffa87a5a036c874d424ee675dfec6b9950fbf77a
│  │  ├─ createdAtEpoch: 205
│  │  ├─ createdAtBlock: 0xa5eae36c97023ef3aea6ce13a2404e4d97abea72301365d3f85c68b780267260
│  │  ├─ closedAtEpoch: 230
│  │  └─ closedAtBlock: 0xe3e4f80906098ef2b380ac4dfee4cac2e4a73ae9c888e1b97d8f1a8ae1aca72e (#12976288)
│  └─ POI
│     ├─ submitted: 0xb01c6bbefb55fbea01bb15100ff8b29a23822bcb4c5d3f3a940d5f00aeb05ade

About the Procedure

The Arbitration Charter regulates the arbitration process. You can find it in Radicle project ID rad:git:hnrkrhnth6afcc6mnmtokbp4h9575fgrhzbay

For communications, please use this forum. Additionally, please monitor Graph Protocol’s Discord #arbitration ( ) for any arbitrator reaching out for more information.