Nethermind 1.33 history expiry #2263
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
Author
|
I'll leave this here for a bit. In 1.33 the feature is considered experimental and not to be used in production. Let's err on the side of caution. |
yorickdowne
force-pushed
the
nethermind-1.33
branch
from
1955aea to
3046935
Compare
Collaborator
Author
|
Added pre-cancun-expiry. Rolling remains experimental: I want to enable users to seek it. It's not default. |
yorickdowne
force-pushed
the
nethermind-1.33
branch
from
2b02768 to
e19c3cd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What I did
Support and also require Nethermind 1.33 history expiry. a) online expiry without resync and b) rolling expiry, full 4444