graphprotocol / graphprotocol/graph-node
[Feature] Add support for disabling supports_block_receipts via environment variables
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 1.1k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
Description
Problem
Some blockchain nodes of specific chains return invalid data when calling the eth_getBlockReceipts method. This behavior can cause issues in the functionality of graph-node, particularly when the supports_block_receipts feature cannot be entirely disabled.
Currently, the environment variable GRAPH_ETHEREUM_BLOCK_RECEIPTS_CHECK_TIMEOUT allows configuring the timeout for block receipt checks. However, this is insufficient for completely disabling the functionality.
Proposed Solution
Introduce a new environment variable, such as GRAPH_SUPPORTS_BLOCK_RECEIPTS, to allow disabling the supports_block_receipts feature entirely by setting its value to false.
If the variable is not set, the current default behavior is preserved.
The variable would explicitly override the configuration to skip the supports_block_receipts checks.
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.
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 locating the configuration handling for GRAPH_ETHEREUM_BLOCK_RECEIPTS_CHECK_TIMEOUT and the supports_block_receipts checks; the issue names no files or tests. Add the proposed environment-variable override while preserving the existing default when it is unset, then verify that false skips the checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100