EIP-4844: Force ExternalData arg in state transition fn#4846
Merged
EIP-4844: Force ExternalData arg in state transition fn#4846
Conversation
6c4ca70 to
f9c503c
Compare
Contributor
Performance Report✔️ no performance regression detected Full benchmark results
|
wemeetagain
previously approved these changes
Dec 6, 2022
f9c503c to
fc3fe61
Compare
twoeths
approved these changes
Dec 7, 2022
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 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.
Motivation
State transition function will have two external dependencies: Execution Engine, Data Availability. Current way to handle those is obscure, and optional struct that returns "is payload valid?".
I believe it's necessary to be clear and explicit about this external dependencies and think on each state transition call what are their values
Description