EIP4844: Clarify the use of context bytes in all RPC methods in 4844 #3229
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
AgeManning
changed the title
2 tasks
hwwhww
force-pushed
the
context-bytes-clarification
branch
from
dbabe9e to
0152df2
Compare
hwwhww
force-pushed
the
context-bytes-clarification
branch
from
0152df2 to
95401cf
Compare
djrtwo
approved these changes
Feb 20, 2023
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.
Currently it is slightly ambiguous if context-bytes should be sent along with the new V1 RPC methods in the 4844 spec.
This PR makes it clear that the context bytes should be sent along with all chunks in the RPC methods.