graphprotocol / graphprotocol/graph-node

[Feature] Preventing calls to eth_gettransactionreceipt

Open
#5,891 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area/json-rpc enhancement Stale
Dominant language
Rust
Stars
3.2k
Forks
1.1k
Avg merge
4d 1h
Merged PRs (30d)
1

Description

Description

Hello,

Since the graph-node is supporting eth_getblockreceipts, it is possible to use common node providers at an affordable cost.
In order to prevent the bill to explode because the indexer for some reason failed to detect the eth_getblockreceipts availability, I don't want to use eth_gettransactionreceipt, I prefer stop indexing for this provider.

Im' in stress every time the indexer restarts, I have to watch if the eth_getblockreceipts is detected because sometimes, for some reasons it isn't.

Do you think it's possible to prevent eth_gettransactionreceipt ?

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing graph-node's handling of eth_getblockreceipts capability detection and its fallback to eth_gettransactionreceipt. Define how a provider can refuse the fallback and what indexing behavior should result when eth_getblockreceipts is unavailable; confirm the behavior with tests for provider capability detection and indexing stoppage.

Written by the indexing model from the issue text.

Assessment

Tech stack
blockchain, rust
Domain
backend, blockchain
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.