This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
Add stakeworld bootnodes for polkadot, kusama and westend #7148
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.
Hi,
I have setup bootnodes for polkadot, kusama and westend. I also collected some information from previous pr's and did a writeup on setting up bootnodes here.
The bootnodes are hosted on dedicated servers. For every chain the bootnode is accessible via p2p, p2p/ws and p2p/wss with a valid certificate (nginx proxy/letsencrypt).
The node-key is backed up and can be restored to a new server in case of server problems.
All network paths were checked by running
polkadot --chain <chain> --base-path /tmp/node --no-hardware-benchmarks --name "Bootnode testnode" --reserved-only --reserved-nodes "<path>"
and seeing if we got a connected node.For example for polkadot:
This was also done on kusama and westend.
If there are any questions or remarks of course let me know.
Regards,
Max | stakeworld.io