feat: add more beacon API types #5292
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
mattsse
added
C-enhancement
mattsse
requested review from
rkrasiuk and
Rjected
and removed request for
Rjected
mattsse
force-pushed
the
matt/beacon-glue
branch
from
2f0b84a
to
e134a03
Compare
mattsse
force-pushed
the
matt/beacon-glue
branch
3 times, most recently
from
e33fae8
to
c75f248
Compare
mattsse
force-pushed
the
matt/beacon-glue
branch
from
c75f248
to
2dcab8e
Compare
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.
adds relay api types
adds a lot of glue code to support beacon API serialization, this allows us to reuse the same executionpayload types for beacon API
if this turns out to be bad DX, we can just duplicate them..., we definitely need an additional builder type
also moves some stuff around