graphprotocol / graphprotocol/graph-network-subgraph
block numbers in arbitrum deployment appear bugged
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 82
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
when querying allocations from https://thegraph.com/hosted-service/subgraph/graphprotocol/graph-network-arbitrum - the fields createdAtBlockNumber and closedAtBlockNumber appear to return invalid values - e.g. this result:
"allocations": [
{
"id": "0x0001b044ebd481afef0545f431fe275980e69e09",
"createdAtBlockNumber": 18176693,
"createdAt": 1695207989
},
that timestamp is for today, but that blocknumber was in 2022 on arbitrum
Can anyone from the foundation plz advise? I believe this is a bug in the subgraph
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 reproducing the allocation query against the linked Graph hosted-service subgraph and compare createdAtBlockNumber and closedAtBlockNumber with their timestamps on Arbitrum. Trace how these fields are populated in the subgraph and smart-contract sources mentioned by the repository description; the issue is done when the returned block numbers match the corresponding timestamps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100