-
Notifications
You must be signed in to change notification settings - Fork 5
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
published ENRs do not contain the UDP port #48
Comments
Indeed, we do not have it enabled:
|
jakubgs
added a commit
that referenced
this issue
May 10, 2022
#48 Signed-off-by: Jakub Sokołowski <[email protected]>
Done: e4642a51
|
We can see here how the ENR record changed: Before
After
The |
|
Nice. Thank you :). LGTM! The ENRs on fleets.status.im show the discv5 ENR now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The ENRs made available in #42 do not contain the UDP port.
The cause might be that discv5 is not enabled on the fleet nodes. If
--discv5-discovery=false
, which is the default, only DNS related ENRs are available.Currently,
nwaku
manages two separate ENRs, see waku-org/nwaku#915The json RPC call returns the discv5 related ENR; only if discv5 is disabled, it will return the DNS related ENR.
cc @jakubgs @jm-clius
(Further, only the jenkins pipeline for the status-test fleet has the
-d:discv5_protocol_id:d5waku
. This unrelated to this issue, but necessary for Waku discv5 operation. The other fleets would need that parameter set, too)The text was updated successfully, but these errors were encountered: