Skip to content

Update EIP-7702: Move to Review #8657

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

Merged
eth-bot merged 4 commits into from
Jun 17, 2024
Merged

Update EIP-7702: Move to Review #8657

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
f6349f8
Update eip-7702.md
timbeiko Jun 12, 2024
f9fe8e5
7702: rm link to 5003
lightclient Jun 17, 2024
ea7176d
7702: fix typo
lightclient Jun 17, 2024
1b1bb17
7702: fix typo
lightclient Jun 17, 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
4 changes: 2 additions & 2 deletions EIPS/eip-7702.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ title: Set EOA account code for one transaction
description: Add a new tx type that sets the code for an EOA during one transaction execution
author: Vitalik Buterin (@vbuterin), Sam Wilson (@SamWilsn), Ansgar Dietrichs (@adietrichs), Matt Garnett (@lightclient)
discussions-to: https://ethereum-magicians.org/t/eip-set-eoa-account-code-for-one-transaction/19923
status: Draft
status: Review
type: Standards Track
category: Core
created: 2024-05-07
Expand Down Expand Up @@ -147,7 +147,7 @@ Specifically:
* Hence, it avoids the problem of "creating two separate code ecosystems", because to a large extent they would be the same ecosystem. There would be some workflows that require kludges under this solution that would be better done in some different "more native" under "endgame AA", but this is relatively a small subset.
* It does not require adding any opcodes, that would become dangling and useless in a post-EOA world.
* It allows EOAs to temporarily convert themselves into contracts to be included in ERC-4337 bundles, in a way that's compatible with the existing `EntryPoint`.
* Once this is implemented, [EIP-5003](./eip-5003.md) is "only one line of code": just add a flag to not set the code back to empty at the end.
* Once this is implemented, allowing EOAs to migrate permanently is "only one line of code": just add a flag to not set the code back to empty at the end.

## Backwards Compatibility

Expand Down