Execution API alignment #88
Merged
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
I don't understand the comment @LukaszRozmej. This is in the making and I already pivoted to use the same pages as in PagedDb. Updated the description to have it aligned. I don't want to multiply entities here so will reuse for now. |
Minimum allowed line rate is |
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.
This PR introduces a new functionality that is aligned to how the Execution Client works. It embraces the notion of
NewPayloadandForkChoiceUpdateby introducing a possibility of tracking multiple chains at the same time. OnceFCUpublishes the final hash, it's pushed down to the storage with all the preceding blocks. This means that for allheadchanges, the change is done without involvement of the underlying database.The PR includes an updated
design.mddocument that covers the changes.