feat: make beacon bridge use Electra variants#1807
Merged
Conversation
1 task
looks good
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
2 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.
This is a followup of #1801
What was wrong?
Beacon Bridge will stop working after Pectra fork.
How was it fixed?
Update our types to be Pectra instead of Deneb.
NOTE: We don't have a way to test these endpoints until the fork, as they would fail (except in some cases when format didn't change).
Ideally, we should be able to decode/deserialize correct version and it's something I will work on. But I don't have time to do it until the fork.
This code can/should be deployed as soon as the fork happens on mainnet.
To-Do