You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
proofOfIndexing
requests, similarly to regular subgraph queriesAre 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
The text was updated successfully, but these errors were encountered: