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
Right now nonces are just used for checking a certain preauthorized payload be executed just once, while also allowing for executing different times the same preauth action (with different signatures, of course)
As proposed in this EIP comment, it could be interesting to treat nonces below a certain x threshold (x = 10 ^ 10 seems good enough) as an incremental nonce. This means that a preauthorized transaction that has a nonce n below x, will only be executed iff last executed preauth tx for that address was n - 1.
It would require adding an additional storage key for keeping track of address nonces.
The text was updated successfully, but these errors were encountered:
Right now nonces are just used for checking a certain preauthorized payload be executed just once, while also allowing for executing different times the same preauth action (with different signatures, of course)
As proposed in this EIP comment, it could be interesting to treat nonces below a certain
x
threshold (x = 10 ^ 10
seems good enough) as an incremental nonce. This means that a preauthorized transaction that has a noncen
belowx
, will only be executed iff last executed preauth tx for that address wasn - 1
.It would require adding an additional storage key for keeping track of address nonces.
The text was updated successfully, but these errors were encountered: