fix: remove enr padding #16
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
|
According to sigp/lighthouse#4530 (comment), the following ENRs are also invalid:
Do we know why? |
They seems to work on my side, I was able to get mentioned error only for |
filoozom
reviewed
Sep 16, 2023
filoozom
approved these changes
Nov 1, 2023
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.
This PR address prysm bootnode ENR fix. This ENR string contains padding containes padding (
==), which doesn’t correspond encoding scheme that declared in EIP-778.Jobs:
enr-cli, also checks that all non-empty and non-comment strings are ENR stringsJob triggers on PR to the main branch.