I understand. There are two points I’d like to address in this draft:
-
The contract should be able to revoke a previously registered fee increase request. In other words, I think we should abstract this capability into the protocol: the contract code should decide whether or not to increase the fee, while the protocol is only responsible for providing the mechanism to execute that decision.
-
If the goal is to allow ERC-20 tokens to track transactions across multiple executions, I think it would be better, at least in the short term, to pursue block-scoped storage or multi-block data storage proposals, such as the ones below. I prefer this approach because it adds a capability to the protocol rather than imposing a specific constraint. The contract can then decide how and when to make use of that capability.
Alternatively, we could use persistent storage. While it is somewhat more expensive, the lower gas costs expected after Glamsterdam should make this trade-off more reasonable.