algonet: use lower value of LastPartKeyRound for bootstrappedScenario #3865
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.
Summary
The genesis.json file in the bootstrappedScenario specifies 3M for LastPartKeyRound, which can take many hours to generate 100 participation & falcon keys for a 3M round range when running this scenario using algonet (via "netgoal build").
This lowers the round range to 50K which will only take a few minutes, and matches the LastPartKeyRound used in genesis.json for scenario1, scenario2, scenario3. It also modifies the genesis wallet generator to print out how long it took after generating all the keys, if verbose mode is on.
Test Plan
Existing tests should pass.