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.

Sign up for GitHub

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

Jump to bottom

Make use of separate discovery port #4888

Open

marcindsobczak opened this issue Nov 10, 2022 · 0 comments

Labels

discovery network refactoring

Contributor

marcindsobczak commented Nov 10, 2022

Is your feature request related to a problem? Please describe.
We had issue (#4876) with parsing discovery port. It was fixed (#4886), now we are able to parse data as spec says (https://ethereum.org/en/developers/docs/networking-layer/network-addresses/#enode), but we are not using this additional port

Describe the solution you'd like
Refactor our code to use separate discovery port

marcindsobczak added refactoring network discovery labels

marcindsobczak mentioned this issue

Fix enode parsing #4886

Merged

12 tasks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment