graphprotocol / graphprotocol/indexer
Feature request : prevent ETH leaking - max ratelimit
@Jannis is already working on this.
Since Oct 30, 2020.
- Dominant language
- TypeScript
- Stars
- 262
- Forks
- 148
- PR merge metrics
- No merged PRs in 30d
Description
Some bugs and some operator misconfigurations cause a tx spam, regardless the various reasons, it means ETH is getting spent as gas. This can quickly add up and on mainnet this could be expensive.
I'd like protection against this, by setting a max spending limit per timeframe (ratelimit), that every spending gets checked against. One option would be to work out what expected spending would be in regular operations and say double that. Another option would be to let the operator set the amount (with the risk they set it to low for normal operations).
Contributor guide
No contributing guide indexed for this repository
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.
Assessment
This issue has not been assessed yet.