graphprotocol / graphprotocol/graph-node
L1/L2 Block Numbers
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 1.1k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
Pablo chatted with Juan and Ariel about something in the network subgraph that will be a problem on Arbitrum: basically, that block numbers in L2 are a bit messy and (as far as we know) the graph node doesn't surface L1 block numbers to subgraph mappings.We think we have a workaround for now but it might have awful performance, and this will also affect subgraphs in Arbitrum for our users when we add support for that chain on the network. So I was wondering if we could chat about getting this into the roadmap for the graph node team at some point. (Discussed n Jan 17, 2023 Graph Node standup with Pablo.)
Contributor guide
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
The issue concerns L1/L2 block-number mappings in Graph Node for Arbitrum, but names no files, tests, or entry points. Start by reviewing the network subgraph workaround and the current Graph Node behavior; done would require a decided roadmap or implementation scope for exposing the needed mapping without unacceptable performance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain
- Domain
- blockchain, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100