Skip to content
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

Support resolving bootnode ENR by http query #329

Closed
corverroos opened this issue Mar 31, 2022 · 0 comments
Closed

Support resolving bootnode ENR by http query #329

corverroos opened this issue Mar 31, 2022 · 0 comments

Comments

@corverroos
Copy link
Contributor

Problem to be solved

ENRs are long complex things that are calculated from p2pkeys and runtime IP addresses, this makes them hard to configure.

Configuring bootnode ENRs in docker-compose or k8s platforms are especially tricky since IPs are dynamic. The DNS name of a bootnode is however often known within a system (docker-compose/k8s), so this allows nodes to query the bootnode via DNS/http to resolve its ENR.

This approach has been very handy in docker-compose and k8s to resolve bootnode ENRs

Proposed solution

Adds support for querying/resolving bootnode ENRs via http/curl
@corverroos corverroos mentioned this issue Mar 31, 2022
Merged
corverroos added a commit that referenced this issue Apr 1, 2022
@corverroos
p2p: support bootnode ENR querying (#330)
f0bfb31 
Adds support for querying/resolving bootnode ENRs via http/curl. This approach has been very handy in docker-compose and k8s to resolve bootnode ENRs. Since ENRs are long complex things that are calculated from p2pkeys, they are hard to configure. The DNS name of a bootnode is however often known within a system (docker-compose/k8s), so this allows nodes to query the bootnode via http to resolve its ENR.

Bootnode ENR can already be provided in two formats: `enr:` and `enode:`, this adds a third basically `http`.

category: feature 
ticket: #329
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@corverroos