-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Add EIP: History Expiry Meta #9572
Conversation
✅ All reviewers have approved. |
EIPS/eip-history-expiry-meta.md
Outdated
|
||
### 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. |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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.
EIPS/eip-history-expiry-meta.md
Outdated
|
||
## Rationale | ||
|
||
### Why wait for Pecra |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
### Why wait for Pecra | |
### Why wait for Pectra |
What is the correct way to get an EIP numbers assigned for this? |
One of the admins will notice it and assign a number 🙏 |
@SamWilsn @g11tech @abcoathup can we get an eip number here please? |
Co-authored-by: g11tech <develop@g11tech.io>
The commit d921b28 (as a parent of 56140e5) contains errors. |
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. |
@pipermerriam it just needs one approval from on of the rditors and it will be merged |
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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. |
Execution clients may test dropping of history on devnets for all history prior to block `TODO-WHAT-BLOCK-NUMBER?`. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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?`. | |
There was a problem hiding this 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...
Meta-EIP for History Expiry that gathers all of the information and related EIPs into a single place.