Timeline for Best practice upgrading bootnodes
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 28, 2022 at 11:14 | history | edited | Bruno♦ |
edited tags
|
|
| May 20, 2022 at 4:36 | comment | added | Purple_Turtle |
It depends then on what method are your users running. Are they running the node with a flag such as --mainnet, if so then yes what you say is the right way, but then users would have to download more data as compared to simply downloading a chainspec. on the other hand if you are just distributing the chainspec, there's no need for any of that.
|
|
| May 19, 2022 at 19:09 | comment | added | Dubs | because we need to distribute it on the complete network ( more than 300 nodes ) and not on a dev one. | |
| May 19, 2022 at 13:16 | comment | added | Purple_Turtle |
Why would you want to recompile if you're only changing the bootnode address? Just make the relevant changes in the generated chain spec file and you should be good to go. Also on preexisting nodes that are syncing you can pass the new peer id address with the --bootnodes flag.
|
|
| May 19, 2022 at 12:08 | history | asked | Dubs | CC BY-SA 4.0 |