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

Add EIP: Retroactively Included EIPs #8389

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Add EIP: Retroactively Included EIPs #8389

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
e779059
Create Retro Meta EIP
timbeiko Apr 4, 2024
e5859d7
whitespace
timbeiko Apr 4, 2024
18ca7cc
Number and link
timbeiko Apr 4, 2024
fae5d1b
Update EIPS/eip-7675.md
timbeiko Apr 18, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
52 changes: 52 additions & 0 deletions EIPS/eip-7675.md
View file
Open in desktop
@@ -0,0 +1,52 @@
---
timbeiko marked this conversation as resolved.
Show resolved Hide resolved
eip: 7675
title: Retroactively Included EIPs
description: Core EIPs activated independently of an Ethereum hard fork.
author: Tim Beiko (@timbeiko)
discussions-to: https://ethereum-magicians.org/t/eip-7675-retroactively-included-eips/19541
status: Draft
type: Meta
created: 2024-04-04
requires: 2681, 3607, 7523, 7610
---

## Abstract

This Meta EIP lists Core EIPs introducing changes to Ethereum's consensus which were activated independently of an Ethereum hard fork due to their backward compatible nature. These EIPs generally introduce constraints to underspecified protocol rules or clarify how certain edge cases should be handled.

## Motivation

To maintain consensus across all nodes, backward incompatible changes to Ethereum must be activated synchronously. Given the coordination required for this, changes are usually bundled together in network upgrades. A Meta EIP is typically used to list the changes included in a network upgrade, as well as its activation time.

However, backward compatible consensus changes do not require a network upgrade to be activated. For example, if a consensus rule is underspecified, an EIP can propose a constraint to bound it. If the constraint was never broken in Ethereum's history and is unlikely to be broken in the future, the EIP can be considered backward compatible. It could then be "retroactively activated", as both nodes which support the change and those which do not would agree on the current network state and history.

This Meta EIP lists all such EIPs which core developers have retroactively included as part of the Ethereum protocol specification.

## Specification

### Retroactively Activated EIPs

* [EIP-2681](./eip-2681.md): Limit account nonce to 2^64-1
* [EIP-3607](./eip-3607.md): Reject transactions from senders with deployed code
* [EIP-7523](./eip-7523.md): Empty accounts deprecation
* [EIP-7610](./eip-7610.md): Revert creation in case of non-empty storage

### Activation

All EIPs listed above are considered activated as of Ethereum's genesis block. Note that EIP-7523 distinguishes pre- and post-merge behavior on the Ethereum mainnet.

## Rationale

This Meta EIP provides a global view of all changes included in the Ethereum protocol without an explicit network upgrade, as well as links to full specification.

## Backwards Compatibility

No backward compatibility issues found.

## Security Considerations

None.

## Copyright

Copyright and related rights waived via [CC0](../LICENSE.md).