Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AA-306: Add warning on changed expectations for 7712 and 7702 combination #39

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions RIPS/rip-7712.md
Original file line number Diff line number Diff line change
Expand Up @@ -128,6 +128,16 @@ Smart Contract Accounts could access the `uint256 nonce` value in the `Transacti
higher 192 bits assuming nonce cannot exceed 64 bits.
This assumption is wrong and is broken by the proposed change.

### EIP-7702 authorization revocation with a nonce bump

In EIP-7702 the EOA is able to revoke an "authorization tuple" it has previously signed as long as it has not been
included on-chain.
This can be done by incrementing the EOAs `nonce`, which in turn can only be done by sending a new transaction.
With RIP-7712, however, there exists a new way of sending a transaction without affecting the legacy `nonce` field.
Such a transaction will not invalidate the previously signed "authorization tuple" either.
Users who are unaware of this change may not expect an "authorization tuple" to remain valid after sending a different
transaction and should be aware of the existence of RIP-7712 and multidimensional nonces.

## Security Considerations

Smart Contract Accounts that need to enforce the sequence of transaction execution must apply appropriate restrictions
Expand Down