forked from dashpay/dash
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge dashpay#6225: feat: bury v20 fork - fire up test chains by firs…
…t block - 4/n 2381255 fix: possible deadlock during calculation of signals for historical blocks during re-index (Konstantin Akimov) 1087489 feat: bury v20 deployment (Konstantin Akimov) 64cedb3 feat: actually test something EHF unit tests (Konstantin Akimov) 762a808 chore: drop irrelevant bip9 code from feature_llmq_rotation.py (Konstantin Akimov) 7735631 fix: remove v20 from test feature_llmq_evo as far as mn_rr used (Konstantin Akimov) ca83b26 fix: crash in CreditPool: it meant to check that DIP0003 is activated (Konstantin Akimov) Pull request description: ## Issue being fixed or feature implemented V20 is activated on mainnet: time to bury it! dashpay#6186 ## What was done? Hard-fork v20 is buried and it requires to implement multiple fixes, simplifications, refactoring: - some tests for EHF moved from functional tests to unit tests - fixed crash in Credit Pool if DIP3 is not activated yet - added a requirement for v20 activation for `CMNHFManager::GetSignalsStage` - removed useless code from functional test feature_llmq_rotation - renamed variables "v20" to "mn_rr" in feature_llmq_evo.py so far as actually used fork is mn_rr ## How Has This Been Tested? Some unit and functional tests to succeed. Done reindex (just in case): src/qt/dash-qt -reindex -assumevalid=0 src/qt/dash-qt -reindex -assumevalid=0 -testnet ## Breaking Changes N/A ## Checklist: - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [x] I have added or updated relevant unit/integration/functional/e2e tests - [x] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone ACKs for top commit: UdjinM6: ACK 2381255 PastaPastaPasta: utACK dashpay@2381255 Tree-SHA512: eec35745baa695f3f286d39b6a61fa0a9f34820b13d1dd4cfbd1efe707850283892c39bf7fe49c49c812e0c02465d64df11480b3f12aa7f21b59a71eeae7260e
- Loading branch information
Showing
18 changed files
with
85 additions
and
194 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
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.