graphprotocol / graphprotocol/graph-node
Issue: Subgraph Indexing Only Block Data Should Not Require a Contract Address in the Manifest
Open
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
Currently, the subgraph indexing process requires a contract address to be specified in the manifest, even when the block data does not necessarily depend on a specific contract. This restriction limits flexibility, especially in cases where the subgraph is indexing non-contract-related block-level data.
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
Start by tracing manifest validation and the subgraph indexing path for block-only data. Confirm where the contract address is required and define the manifest behavior that should allow block data without one; done means such a subgraph can be accepted and indexed without a contract address.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100