graphprotocol / graphprotocol/graph-node

[Feature] POI request logging for dispute investigation

Open
#5,767 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement Stale
Dominant language
Rust
Stars
3.2k
Forks
1.1k
Avg merge
4d 1h
Merged PRs (30d)
1

Description

Description

A number of recent network dispute cast a doubt on the parameters used for POI generated (epoch, block number, presence of determinism error). Currently, graph-node does not log the graphql proofOfIndexing requests, and does not log the parameters ultimately used for the computation of the POI.

For indexers to be able to prove that they properly closed an allocation, graph-node should be logging:

  • The proofOfIndexing requests, similarly to regular subgraph queries
  • If it cannot compute the POI for the requested subgraph and block, graph-node should log the situation, and, if the error is a determinism error, log which block it picked to generate the POI.
Are you aware of any blockers that must be resolved before implementing this feature? If so, which? Link to any relevant GitHub issues.

No response

Some information to help us out
  • Tick this box if you plan on implementing this feature yourself.
  • I have searched the issue tracker to make sure this issue is not a duplicate.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the GraphQL proofOfIndexing request handling and the existing logging path for regular subgraph queries. Done means logging POI requests, reporting when a POI cannot be computed, and recording the selected block when the failure is a determinism error.

Written by the indexing model from the issue text.

Assessment

Tech stack
graphql, rust
Domain
api, observability
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.