-
Notifications
You must be signed in to change notification settings - Fork 58
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
chore: update resolved enr ip when using dns4-domain-name
flag
#1576
Labels
Comments
Weekly Update
|
3 tasks
Weekly Update
|
Weekly Update
|
Weekly Update
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Background
When using
dns4-domain-name
egThe node creates an ENR with ip
0.0.0.0
and the multi is constructed using that ip/ip4/0.0.0.0/tcp/60000/p2p/16Uiu2HAmFj9mVkzj81XBFTVK1475iKoPPiakdgZtoPTtPaTYqqRy
.Example of the generated ENR with the above command (decode it here)
The thing is that since discv5 doesn't understand our
multiaddrs
field, this node won't be discoverable by disv5, since the address that is being advertised is0.0.0.0
.In other protocols using libp2p and discv5 (eg Ethereum) the address that is advertised in the enr is the ip that results of resolving
dns4-domain-name
.Example. In prysm using the following, will lead to an ENR that contains the IP that resolved from google.com. See logs:
Acceptance criteria
./build/wakunode2 --dns4-domain-name=some_domain
the constructed ENRip
field contains the resolved IP instead of just0.0.0.0
.The text was updated successfully, but these errors were encountered: