This repository was archived by the owner on Nov 25, 2025. It is now read-only.
Add freezer code from upstream #310
Closed
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Why this should be merged
Adds functionality from upstream. This functionality is referenced from the new pbss scheme and it seems more aligned to take this code. This is a no-op behavior change.
Additionally with the chain directory we can consider implementing the functionality.
How this works
Takes code from upstream
Slightly modifies our wrapper
Replaces memdb.New() -> rawdb.NewMemoryDatabase() where relevant (the latter implements the ethdb.Database interface including the freezer)
How this was tested
CI