You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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).
The text was updated successfully, but these errors were encountered: