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.

Sign up for GitHub

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

Jump to bottom

Update EIP-7702: selfdestruct opcode behaviour change in eip-7702 #8832

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
+6 −0
Open

Update EIP-7702: selfdestruct opcode behaviour change in eip-7702 #8832

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
abd61ba
eip-7702: move the lighter check up
sudeepdino008 Jun 25, 2024
9179883
selfdestruct opcode behaviour change in eip-7702
sudeepdino008 Aug 28, 2024
ab79897
respond to comments
sudeepdino008 Aug 28, 2024
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
6 changes: 6 additions & 0 deletions EIPS/eip-7702.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -120,6 +120,12 @@ The main families of instructions where a ban was considered were storage relate

Creation instructions were considered for a ban on other similar EIPs, however because this EIP allows EOAs to spend value intra-transaction, the concern with bumping the nonce intra-transaction and invalidating pending transactions is not significant. A neat byproduct of this is that by combining EIP-7702 and CREATE2 it will be possible to commit to deploy specific bytecode to an address without committing to any fee market parameters. This solves the long standing issue of universal cross-chain contract deployment.

### Behaviour of SELFDESTRUCT opcode

[EIP-6780](./eip-6780.md) restricted SELFDESTRUCT opcode behaviour, allowing account data deletion only if the account was created in the same transaction. A 7702 transaction essentially allows code to be assigned to an EOA. The subsequent execution of such code in the same transaction can cause the EOA to selfdestruct, causing account data deletion, leading to issues like transaction replay.

To prevent problems arising from EOAs selfdestructing, this EIP updates the opcode behaviour, which will not delete account data for EOAs with delegated designation.

### Signature structure

The signature scheme in this EIP supports flexible design patterns, allowing for both full delegation to `address` and more protected delegations to `address`.
Expand Down
Loading