Receive enodes over websockets and serve them at /static-nodes.json #361
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Intention is to make `eth-netstats` a source of Auto-updated Enode List to use with Nethermind of example. How it works: The enode-reporter is a separate NodeJS app that is designed to run besides Nethermind and query the Nethermind client via JsonRPC. Then it publishes enode and name on the `enode` channel via Websockets connection with `eth-netstats`. Here we collect all enodes (keyed on node id for deduplication purposes) and store them in the format of `static-nodes.json`, one of the config files for Nethermind. The file is available at `/static-nodes.json`.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Intention is to make
eth-netstatsa source of Auto-updated Enode Listto use with Nethermind of example.
How it works: The enode-reporter is a separate NodeJS app that is designed to run
besides Nethermind and query the Nethermind client via JsonRPC. Then it publishes enode and name
on the
enodechannel via Websockets connection witheth-netstats. Here we collect allenodes (keyed on node id for deduplication purposes) and store them
in the format of
static-nodes.json, one of the configfiles for Nethermind.
The file is available at
/static-nodes.json.