Skip to content

Add EIP: History Expiry Meta #9572

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

Merged

Conversation

pipermerriam
Copy link
Member

@pipermerriam pipermerriam commented Mar 31, 2025

Meta-EIP for History Expiry that gathers all of the information and related EIPs into a single place.

@github-actions github-actions bot added c-new Creates a brand new proposal s-draft This EIP is a Draft t-meta labels Mar 31, 2025
@eth-bot
Copy link
Collaborator

eth-bot commented Mar 31, 2025

✅ All reviewers have approved.

@eth-bot eth-bot added e-consensus Waiting on editor consensus e-review Waiting on editor to review labels Mar 31, 2025
@eth-bot eth-bot changed the title Add history expiry meta eip Add EIP: History Expiry Meta Mar 31, 2025
@github-actions github-actions bot added the w-ci Waiting on CI to pass label Mar 31, 2025

### Full History Sync

Execution layer clients will no longer be able to implement a full historical sync of history from the DevP2P network. Clients that wish to retain this functionality will need to source the pre-merge blocks from an alternate source. Clients SHOULD ensure that they continue to correctly validate block data sourced from alternate locations.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that should still be possible with 7801 which uses DevP2P

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm gonna add a section above about 7801 to the list of alternate sources for this data, and be more specific here that this is about the eth protocol.


## Rationale

### Why wait for Pecra
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### Why wait for Pecra
### Why wait for Pectra

@pipermerriam pipermerriam marked this pull request as ready for review April 1, 2025 19:45
@pipermerriam pipermerriam requested a review from eth-bot as a code owner April 1, 2025 19:45
@pipermerriam
Copy link
Member Author

What is the correct way to get an EIP numbers assigned for this?

@github-actions github-actions bot added w-ci Waiting on CI to pass and removed w-ci Waiting on CI to pass labels Apr 1, 2025
@smartprogrammer93
Copy link
Contributor

What is the correct way to get an EIP numbers assigned for this?

One of the admins will notice it and assign a number 🙏

@github-actions github-actions bot removed the w-ci Waiting on CI to pass label Apr 8, 2025
@smartprogrammer93
Copy link
Contributor

@SamWilsn @g11tech @abcoathup can we get an eip number here please?

Copy link

The commit d921b28 (as a parent of 56140e5) contains errors.
Please inspect the Run Summary for details.

@github-actions github-actions bot added the w-ci Waiting on CI to pass label Apr 10, 2025
@github-actions github-actions bot removed the w-ci Waiting on CI to pass label Apr 10, 2025
@pipermerriam
Copy link
Member Author

I believe I've cleaned up all of the validation errors. The run seems to be hanging due to being on a fork. Let me know if there's anything i need to do to resolve this.

@smartprogrammer93
Copy link
Contributor

@pipermerriam it just needs one approval from on of the rditors and it will be merged

@pipermerriam
Copy link
Member Author

Can we get a review-and-or-merge of this?


### Testnet Activation

Testing of history expiry will occur on the Sepolia testnet. Execution clients may begin dropping pre-merge Sepolia history on 2025-05-01.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Testing of history expiry will occur on the Sepolia testnet. Execution clients may begin dropping pre-merge Sepolia history on 2025-05-01.
Testing of history expiry will occur on the Sepolia testnet. Execution clients MAY begin dropping pre-merge Sepolia history on 2025-05-01.

Comment on lines +46 to +47
Execution clients may test dropping of history on devnets for all history prior to block `TODO-WHAT-BLOCK-NUMBER?`.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Execution clients may test dropping of history on devnets for all history prior to block `TODO-WHAT-BLOCK-NUMBER?`.
Execution clients MAY test dropping of history on devnets for all history prior to block `TODO-WHAT-BLOCK-NUMBER?`.

@eth-bot eth-bot enabled auto-merge (squash) April 18, 2025 19:51
Copy link
Collaborator

@eth-bot eth-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All Reviewers Have Approved; Performing Automatic Merge...

@eth-bot eth-bot merged commit b3dc8b5 into ethereum:master Apr 18, 2025
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c-new Creates a brand new proposal e-consensus Waiting on editor consensus e-review Waiting on editor to review s-draft This EIP is a Draft t-meta
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants