graphprotocol / graphprotocol/graph-node
[Feature] Figure out how to charge gas for declared calls
Open
Nobody has claimed this yet.
area/indexing
enhancement
Stale
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 1.1k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
The implementation of declared calls (#5264) does not charge gas when the call is made before running the handler. It will charge gas when the handler actually executes ethereum.call, but that leaves a small gap for calls that are declared but then never used by the handler.
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 reviewing the declared-calls implementation from #5264 and tracing where calls are declared before the handler runs. Compare that path with handler execution of ethereum.call, then identify the relevant tests or entry points for gas accounting. Done means declared calls are charged gas even when the handler never uses them.
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