-
Notifications
You must be signed in to change notification settings - Fork 725
[GUI][BugFix] Masternodes screen, fix impossibility to start Masternodes #2529
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[GUI][BugFix] Masternodes screen, fix impossibility to start Masternodes #2529
Conversation
Fuzzbawls
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK 85b926e
random-zebra
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice catch. We need to backport this to the 5.3 branch. utACK 85b926e and merging...
I believe that's because masternodes can still be individually started with the GUI. |
Correct. Can confirm that I successfully started a masternode through GUI individually using the v5.3.0rc1. |
Hmm, not really. We are doing the same check there, you actually just found another bug :).
So.. the single MN start is working because of another bug actually.. |
|
Yeah... if (!collateralTxAccepted.value(txHash) && walletModel) {
return walletModel->getWalletTxDepth(rec->vin.prevout.hash) > 0;
} |
0e1839e [Refactor] check scriptsig size in CheckBlockSignature (random-zebra) c3ec5e9 [BUG] Correct CCSV opcode handling in script evaluation (random-zebra) fb7e513 [GUI] MasternodesWidget Fix: missing walletModel in mnmodel constructor. (furszy) cbb77f8 Add mainnet DNS seeder from furszy. (furszy) Pull request description: Back porting the last PRs for the coming v5.3.0 production release: List: * #2524. * #2529. * #2532. ACKs for top commit: Fuzzbawls: utACK 0e1839e random-zebra: utACK 0e1839e Tree-SHA512: 2dd07b0cc79b5a2f2791393ad37ed369bc72ac3450d168befc812bb8cf1336f3b59ef4d3cce6f346eeb1b2d826368c2cae3ccc04ee82b807958e6479ca6ae95b
… MNModel::data f0fd8ac Refactor: remove duplicated coll. confirmation check in MNModel::data (random-zebra) Pull request description: Follow up to the discussion in #2529. If walletModel is null, then `MNModel::data` returns true at `WAS_COLLATERAL_ACCEPTED`. Fix the bug removing the duplicated check (`getWalletTxDepth > MasternodeCollateralMinConf()` is already checked every 30 seconds in `MNModel::updateMNList`). ACKs for top commit: furszy: utACK f0fd8ac Fuzzbawls: utACK f0fd8ac Tree-SHA512: 63065b4ae40403107d738d25ebf6616e99df4373b5fbe4d6b924fecddeef4189f455a91e1cbb48e8c85458481ab519420b49210d6e9f5284c6f35c6e53b35d4e
Fix impossibility to start Masternodes using the GUI.
This was introduced by beb1cf6 (curiously enough, no one noticed it up until now..), the
walletModelis provided to the widget inloadWalletModel, so it can't be used in theMasternodesWidgetconstructor to construct themnmodelobject.