-
Notifications
You must be signed in to change notification settings - Fork 922
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to Discovery V5.1 #7302
Update to Discovery V5.1 #7302
Conversation
Codecov Report
@@ Coverage Diff @@
## master #7302 +/- ##
==========================================
- Coverage 61.81% 61.58% -0.24%
==========================================
Files 424 424
Lines 30110 29815 -295
==========================================
- Hits 18614 18362 -252
+ Misses 8538 8512 -26
+ Partials 2958 2941 -17 |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
@nisdas is this needed for Zinken? |
This pull request has been closed due to inactivity. Please reopen this pull request if you would like to continue working on it. |
… into discoveryV5.1
_ = []interface{}{ | ||
&pubkey, | ||
&withdrawalCredentials, | ||
&amount, | ||
&signature, | ||
&index, | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No longer need this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. We have two catdog bootnodes and I was able to find peers successfully.
What type of PR is this?
Feature Addition
What does this PR do? Why is it needed?
Updates Prysm to use DiscoveryV5.1 inline with this issue:
ethereum/consensus-specs#2059
Which issues(s) does this PR fix?
N.A
Other notes for review