Skip to content

Update EIP-7723: Update 7723 to include EELS/EEST in CFI #9290

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 7 commits into from
Mar 14, 2025
Merged

Update EIP-7723: Update 7723 to include EELS/EEST in CFI #9290

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
5c84565
Update 7723 to include EELS/EEST in CFI
marioevz Jan 30, 2025
d20d9b5
suggestions
marioevz Jan 30, 2025
1c3fd5d
Paraphrasing
marioevz Feb 12, 2025
d38d9a6
ACD comments
marioevz Feb 13, 2025
4898448
fix links
marioevz Feb 13, 2025
a39a049
fix links 2
marioevz Feb 13, 2025
d67d3b1
EIP updates
marioevz Feb 24, 2025
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
8 changes: 8 additions & 0 deletions EIPS/eip-7723.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,10 @@ Non-Core EIPs that are `Considered for Inclusion` **SHOULD** be supported prior

An EIP **MAY** be moved from `Considered for Inclusion` to `Declined for Inclusion` if client teams are against including the EIP in the network upgrade.

An EIP **SHOULD** have a Python implementation in [execution-specs](https://github.com/ethereum/execution-specs/blob/78fb726158c69d8fa164e28f195fabf6ab59b915/README.md), submitted as an open PR, along with corresponding tests in [execution-spec-tests](https://github.com/ethereum/execution-spec-tests/blob/38621dc8f2cbc80a096e0906b28e4d4984752501/README.md), also submitted as an open PR. The EIP writer is encouraged to reach out to the maintainers of both repositories for assistance with implementation. Client developers **MAY** decide to allow an EIP to be moved to `Considered for Inclusion` without either implementation, being aware that the absence of these implementations could lead to delays in the testing cycle.

Any updates to an EIP that is already at this stage **SHOULD** be accompanied by the appropriate updates to its implementation in [execution-specs](https://github.com/ethereum/execution-specs/blob/78fb726158c69d8fa164e28f195fabf6ab59b915/README.md) and [execution-spec-tests](https://github.com/ethereum/execution-spec-tests/blob/38621dc8f2cbc80a096e0906b28e4d4984752501/README.md) if deemed necessary by client developers.

### Declined for Inclusion

At any time during the network upgrade planning process, client developers **MAY** move EIPs from any other stage to the `Declined for Inclusion` stage if client teams are against including the EIP in the network upgrade. Once a decision is made by client teams to move an EIP to `Declined for Inclusion`, the Upgrade Meta EIP **SHOULD** be updated to reflect this.
Expand All @@ -67,6 +71,10 @@ At any time during the network upgrade planning process, client developers **MAY

When client teams agree to implement a Core EIP in the **next** Upgrade Devnet, the EIP **SHOULD** move to the `Scheduled for Inclusion` stage, and the Upgrade Meta EIP **SHOULD** be updated to reflect this. Non-Core EIPs **SHOULD** move to `Scheduled for Inclusion` when client teams agree to immediately prioritize their implementation.

An EIP **MUST** have a Python implementation in [execution-specs](https://github.com/ethereum/execution-specs/blob/78fb726158c69d8fa164e28f195fabf6ab59b915/README.md), submitted as an open PR or merged to the `devnets/upgradeName/version` branch of the repository, along with corresponding tests in [execution-spec-tests](https://github.com/ethereum/execution-spec-tests/blob/38621dc8f2cbc80a096e0906b28e4d4984752501/README.md), also submitted as an open PR or merged to the `main` branch of the repository. Client developers **MAY** decide to allow an EIP to be moved to `Scheduled for Inclusion` without an [execution-specs](https://github.com/ethereum/execution-specs/blob/78fb726158c69d8fa164e28f195fabf6ab59b915/README.md) implementation, but the tests are strictly mandatory.

Any updates to an EIP that is already at this stage **MUST** be accompanied by the appropriate updates to its implementation in [execution-specs](https://github.com/ethereum/execution-specs/blob/78fb726158c69d8fa164e28f195fabf6ab59b915/README.md) and [execution-spec-tests](https://github.com/ethereum/execution-spec-tests/blob/38621dc8f2cbc80a096e0906b28e4d4984752501/README.md) if deemed necessary by client developers.

`Scheduled for Inclusion` signals that implementation and testing work are underway. The EIP **SHOULD** be included in the network upgrade if no issues arise. The latest Upgrade Devnet must contain all `Scheduled for Inclusion` Core EIPs.

An EIP **MAY** be moved from `Scheduled for Inclusion` to `Declined for Inclusion` if client teams are against including the EIP in the network upgrade. An EIP **MAY** also be moved from `Scheduled for Inclusion` to `Considered for Inclusion` if client teams are in favor of including the EIP in the network upgrade but cannot commit to including it in the **next** Upgrade Devnet.
Expand Down
Loading