-
Notifications
You must be signed in to change notification settings - Fork 18
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feature: Genesis executes as a protocol update (#1008)
## Summary Reworked the protocol update triggering, enactment and scenario execution. * Genesis is now a protocol update, and can be automatically resumed. * Scenarios now execute in a separate batch group * Protocol updates can now be triggered immediately after previous updates - so e.g. we don't have to wait till epoch 5 to get cuttlefish activated for testnets and local tests. And now, post-merge-in of #1009 we have a few minor changes: * Removes the name of genesis from `ProtocolConfig`, because it's relied on by static logic, and I don't feel like this is something we should allow people to change (this might break some of our tests/testnets, I'm liaising with Les to discuss) * Updates the testnet configuration to run Anemone/Bottlenose back-to-back at genesis * Changes the testing defaults to: * Run all testnet-configured protocol updates on launch - this means that, by default, tests are running against the latest engine. (This was traditionally too slow to activate before, until we enabled back-to-back configuration). * But don't run scenarios (because this would slow down the tests too much). * Fixes various tests broken by running all protocol updates in our tests In next PRs: * Other Cuttlefish implementation ## Testing * Have tested that genesis can be resumed by stopping it mid-update * I've tested that it can sync stokenet genesis locally
- Loading branch information
Showing
139 changed files
with
3,701 additions
and
1,683 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4,6 +4,7 @@ | |
|
||
# Radix non-versioned files | ||
/**/RADIXDB/ | ||
/**/RADIXDB_OLD/ | ||
/**/NODEMOUNT/ | ||
/**/RADIXDB_TEST/ | ||
/**/logs/ | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -48,6 +48,7 @@ api.users | |
|
||
# radixdlt non-versioned files | ||
RADIXDB/ | ||
RADIXDB_OLD/ | ||
NODEMOUNT/ | ||
RADIXDB_TEST/ | ||
logs/ | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
83 changes: 0 additions & 83 deletions
83
core-rust-bridge/src/main/java/com/radixdlt/environment/ProtocolUpdateScenarios.java
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.