graphprotocol / graphprotocol/indexer
Epoch Manager Subgraph returns wrong latest epoch, inconsistent with epoch/blocks vs The Graph Portal
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 262
- Forks
- 148
- PR merge metrics
- No merged PRs in 30d
Description
What:
Subgraph: https://api.thegraph.com/subgraphs/name/graphprotocol/goerli-epoch-block-oracle
Query:
query network{
networks {
latestValidBlockNumber {
network {
id
}
epochNumber
blockNumber
}
}
}
Returns: latest epoch: 1613
But current/latest epoch is 1612
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the shown GraphQL query against the goerli-epoch-block-oracle subgraph and comparing its latest epoch with the epoch/blocks view in The Graph Portal. Trace the subgraph's epoch and block data sources to identify the discrepancy; it is done when both sources report the same latest epoch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100