Beacon api: propoerly submit blind block #11483
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
terencechain
added
Bug
rkapka
requested changes
Sep 21, 2022
terencechain
force-pushed
the
rpc-submit-blind-block
branch
from
7dbbc31 to
2354109
Compare
Fixed. thanks! |
rkapka
reviewed
Sep 22, 2022
Co-authored-by: Radosław Kapka <[email protected]>
Co-authored-by: Radosław Kapka <[email protected]>
rkapka
approved these changes
Sep 22, 2022
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.
What type of PR is this?
What does this PR do? Why is it needed?
When using beacon API to submit a blind block, it must first go through mev boost/relayer/builder to retrieve the full block. This PR made sure of that. The status duo is to broadcast the blind block, and that's not going to work
Which issues(s) does this PR fix?
Fixes #11477
Other notes for review
N/A