Specify orphaned envelope serving rules#5060
Open
bomanaps wants to merge 3 commits into
Open
Conversation
bomanaps
changed the title
Member
|
Hey there. Sorry this wasn't given a proper review in a timely manner. This sounds reasonable but we would need buy-in from other clients for this to be merged. I'm also missing some context as to why this is important to specify. @nflaig since it appears this was a suggestion of yours, how do you feel about this PR? |
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
3 participants
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.
Specifies orphaned payload serving rules in the Gloas p2p spec for ExecutionPayloadEnvelopesByRange and ExecutionPayloadEnvelopesByRoot, based on points raised by @nflaig in the channel.