Please remove the dynamic bootstrap command line arguments for the Sept 4th network upgrade

Hello Flow node operators,

The Flow Crescendo mainnet network upgrade is coming up on Sept 4th (see announcement). Similar to all previous upgrades (spork), you will have to stop your Flow nodes before the start of the upgrade on that day and then start them again after the upgrade with the new docker tag and the new root block (step 1 and 2 here)

If you have set the dynamic bootstrap command line arguments (--dynamic-startup-access-address, --dynamic-startup-access-publickey, --dynamic-startup-epoch-phase) then please remove them before starting your nodes after the upgrade on Sept 4th (step 2).

The node software has been updated (see pull request) such that it will only allow dynamic bootstrapping for a node that has an empty data folder, if there is no root-snapshot (/public-root-information/root-protocol-state-snapshot.json) file present in the bootstrap folder. If the node detects a root-snapshot file is present, then it will fail to come up with the fatal error message - must specify either a root snapshot file (<path to the file e.g/var/flow/bootstrap/public-root-information/root-protocol-state-snapshot.json>) or Dynamic Startup flags (--dynamic-startup-*) but not both. This is to ensure that the node does not bootstrap from an incorrect root snapshot.

The dynamic bootstrap flags can be added back later if you want to perform a dynamic bootstrap to reclaim disk space or recover your node incase of an issue.

Thank you and we look forward to your support for the upcoming network upgrade.

Flow Foundation

1 Like