Would the overhead be too large if the
SSTORE cost was dynamically calculated for each
tx.origin? Something like
where is the the current SSTORE operation cost for a given EOA
N is the number of storage slot currently used for EOA
The cost doesn’t need to be linear. It seems to me like this creates an incentive for users to “clean” their storage or they pay a premium for every new operation. With this simple scheme, users could, however, just always create new accounts to reset the counter. This could perhaps be mitigated if the first SSTORE is much more expensive and if we use a logarithmic curve instead of a linear one when calculating
The advantages of a scheme like this would be that the UX would be identical as it is now and I believe it would be backward compatible with currently existing contracts.