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.

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

all: tie timestamp based forks to the passage of London #27279

Merged
merged 1 commit into from
May 19, 2023

Conversation

karalabe
Copy link
Member

Certain parts of the code can get weird if some later forks are enabled (Shanghai) before earlier ones (Berlin). This can happen if the chain is full syncing but not yet done, yet we request a pending block.

This PR ties all timestamp based forks to London so that you can only ever enter Shanghai and later if London already passed. This should ensure that we cannot end up in a strange future fork whilst still processing historical blocks.

@karalabe karalabe added this to the 1.11.7 milestone May 16, 2023
Copy link
Contributor

@holiman holiman left a comment

Choose a reason for hiding this comment

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

LGTM

@karalabe karalabe merged commit 85a4b82 into ethereum:master May 19, 2023
devopsbo3 pushed a commit to HorizenOfficial/go-ethereum that referenced this pull request Nov 10, 2023
devopsbo3 added a commit to HorizenOfficial/go-ethereum that referenced this pull request Nov 10, 2023
devopsbo3 added a commit to HorizenOfficial/go-ethereum that referenced this pull request Nov 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants