[WIP] Verkle pathdb rollback #30133
Open
[WIP] Verkle pathdb rollback #30133
+528
−210
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
rjl493456442
requested review from
karalabe,
holiman,
MariusVanDerWijden and
lightclient
as code owners
rjl493456442
force-pushed
the
verkle-pathdb-rollback
branch
from
edd8277 to
5006333
Compare
rjl493456442
force-pushed
the
verkle-pathdb-rollback
branch
from
5006333 to
b70035c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
TODO:
Verkle tree differentiates between zero values and empty values . For instance, a zero storage slot and an empty storage slot are distinct notions in Verkle manner.
Unfortunately, our current state history is insufficient to distinguish between zero and empty values during state rollbacks. The pull request to add this extra information should be merged before this one.