You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
This leaves some inflexibility in adding and removing nodes. Each addition or deletion requires a new client release, which can take a decent amount of time before the changes get rolled out to node operators.
Instead, it would be nice to be able to be able to provide a domain list, such as [https://bootnodes.parity.io, https://bootnodes.polkadot.network], where each domain can list a IPFS CID -> QmY7Yh4UquoXHLPFo2XbhXkhBvFoPwmQUSa92pxnxjQuPU. Fetching this content of this CID would then yield the previous list of bootnode multiaddrs. This approach makes it easier to dynamically add and remove bootnodes to networks at any point (irregardless of client release cycles).
Right now bootnodes are individually defined in the chain spec, like this:
This leaves some inflexibility in adding and removing nodes. Each addition or deletion requires a new client release, which can take a decent amount of time before the changes get rolled out to node operators.
Instead, it would be nice to be able to be able to provide a domain list, such as
[https://bootnodes.parity.io, https://bootnodes.polkadot.network]
, where each domain can list a IPFS CID ->QmY7Yh4UquoXHLPFo2XbhXkhBvFoPwmQUSa92pxnxjQuPU
. Fetching this content of this CID would then yield the previous list of bootnodemultiaddr
s. This approach makes it easier to dynamically add and remove bootnodes to networks at any point (irregardless of client release cycles).CC @bkchr
The text was updated successfully, but these errors were encountered: