Create state abstraction boundaries for write-ops in the state transition #226
Conversation
This file contains 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
DarianShawn
requested review from
abrahamcruise321 and
0xcb9ff9
as code owners
abrahamcruise321
deleted the
feat-seperate-state-abstraction-boundaries
branch
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.
Description
State Transition Functionshould not callCommitfrom theSnapshotinterface and should only return the entries in the state that have been updated. Then, as part of another workflow, these entries would be updated in themerkle trie.The PR is merging from Polygon Edge PR 753
Changes include
Testing