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.
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
[Merged by Bors] - Ipv6 bootnodes #3752
[Merged by Bors] - Ipv6 bootnodes #3752
Changes from 2 commits
402d15c
a4c3b58
818f780
41147b8
8898c3f
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
This means that every bootnode will advertise a udp6 port? And even if we set an ipv4 address in the config, we still create an IPv6 socket right? (There's prob no harm in doing this, just double checking)
I was thinking that we were going to change the
create_enr_builder_from_config()
and if an ipv6 address is given, then we do dual stack and advertise both ips and ports.I see that we want to take the cautious approach and not modify the beacon node in any way, but I think we use regular beacon nodes for bootnodes in the testnets.
What are your thoughts on extending this to include beacon nodes if an ipv6 address is given in the CLI config. We force everyone to use dual-stack initially I think if we went down that path?
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.
I would prefer if we update the boot nodes first tbh. This way we can gauge how ipv6 is working on live discv5 servers and continue from there