[v0.16.x] Backport pending PRs #3670
Merged
Conversation
This file contains hidden or 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
…g governance validation (dashpay#3488) * enable privatesend by default in litemode Signed-off-by: Pasta <[email protected]> * remove useless litemode check in CPrivateSendServer::ProcessMessage, must be MN, so must have litemode off already Signed-off-by: Pasta <[email protected]> * change litemode to mean, doesn't validate governance, but has all other dash features Signed-off-by: Pasta <[email protected]> * litemode must be off for MNs cont Signed-off-by: Pasta <[email protected]> * change litemode help text Signed-off-by: Pasta <[email protected]> * don't skip MN sync in litemode Signed-off-by: Pasta <[email protected]> * drop fLiteMode in bitcoingui.cpp Signed-off-by: Pasta <[email protected]> * skip governance sync in litemode Signed-off-by: pasta <[email protected]> * remove fLiteMode in walletview.cpp Signed-off-by: pasta <[email protected]> * add back Signed-off-by: pasta <[email protected]> * fix comments * fix cache loading * fix scheduled tasks * Fix help text for some rpcs (revert what's left of 3478) Co-authored-by: UdjinM6 <[email protected]>
* Change litemode to disablegovernance, this makes it more clear what that flag actually does. Signed-off-by: pasta <[email protected]> * more fLiteMode to fDisableGovernance Signed-off-by: pasta <[email protected]> * handle -litemode being set Signed-off-by: pasta <[email protected]>
* explicitly check that -disablegovernance is true for pruned mode. Signed-off-by: pasta <[email protected]> * try to set -disablegovernance and -txindex if pruned mode is enabled Signed-off-by: pasta <[email protected]> * Adjust InitWarning when governance validation is disabled Signed-off-by: pasta <[email protected]> * Check for deprecated -litemode earlier * Move -disablegovernance warning into AppInitParameterInteraction * Tweak -prune help text and a related comment in AppInitParameterInteraction * Ignore init warnings in blockchain.py * Adjust "governance validation disabled" warning depending on if running a pruned node Co-authored-by: UdjinM6 <[email protected]> * Skip init warnings in import-rescan.py and node_network_limited.py Co-authored-by: UdjinM6 <[email protected]>
* More accurate fee calculation in CreateDenominated * Apply suggestions from code review Co-authored-by: dustinface <[email protected]> * Fix `finished` conditions Co-authored-by: dustinface <[email protected]>
…dashpay#3589) This also means less smaller denoms (which could be good for privacy) and fixes a bug (not mixing all the available funds), see comments in code for more info.
dashpay#3592) ea65182 [wallet] loadwallet shouldn't create new wallets. (John Newbery) Pull request description: A bug in the initial implementation of loadwallet meant that if the arguement was a directory that didn't contain a wallet.dat file, a new wallet would be created in that directory. Fix that so that if a directory is passed in, it must contain a wallet.dat file. Bug reported by promag (João Barbosa). Tree-SHA512: 0a59fa8a33fde51a88544ad288b00e4995284fe16424f643076aaba42b8244fff362145217650ee53d518dfab7efbed4237632c34cdd3dcbbecaa9ecaab5fd7b Co-authored-by: MarcoFalke <[email protected]>
dashpay#3601) * llqm: Fix thread handling in CDKGSessionManager and CDKGSessionHandler * llmq: Removed unused thread_pool from CDKGSessionManager * Tweak `CDKGSessionHandler::StartThread()` * llmq: Simplify CDKGSessionHandler's thread naming * llmq: Make sure CDKGSessionHandler uses a valid LLMQ type Co-Authored-By: UdjinM6 <[email protected]> Co-authored-by: UdjinM6 <[email protected]>
…ex (dashpay#3606) This indicates a previous crash where the TX made it into the txindex but the block was not flushed to disk. When dashd is restarted then, there is a short time where GetTransaction would return a non-existant block, while callers very often assume that the returned block hash is known.
…string" (dashpay#3609) Having "const char*" leads to undefined behaviour if the "const char*" is deallocated before the thread used it. Co-Authored-By: UdjinM6 <[email protected]> Co-authored-by: UdjinM6 <[email protected]>
* Add spork to change max mixing participants to 20 Signed-off-by: pasta <[email protected]> * Also change min participants on devnet/testnet Signed-off-by: pasta <[email protected]> * adjust formatting Signed-off-by: pasta <[email protected]> * add nPoolNewMinParticipants under regtest Signed-off-by: pasta <[email protected]>
…ashpay#3626) * init: Fix `-litemode` crash due to not connected CClientUIInterface signal Prior to this commit the signal `CClientUIInterface::ThreadSafeMessageBox` is not connected to a slot in Qt at the time its emitted when `-litemode` is used. The signal gets emitted from `InitWarning`, in `InitParameterInteraction`. This happens currently before `BitcoinGUI` gets created by `app.createWindow(networkStyle.data())` in `dash.cpp` where the signal becomes connected to the slot. After this commit the litemode `InitWarning` will be called in `AppInitParameterInteraction` which runs after `BitcoinGUI` has been created, means the signal will be connected then at that point and the crash is fixed. * init: Improve -litemode deprecation warning - Always show a basic warning if `-litemode` gets used no matter if its activated or not. - Let the user know when -disablegovernance gets forced by -litemode.
* Update rpcevo.cpp I would like to mirror docs.dash.org/en/stable/masternodes/maintenance.html#proupservtx by adding the specific term "BLS" to the rpc help menu to differentiate this is not a dash address key like the other ownerkey votingkey. We had this changed on the docs site to help clarify for people who were missing the point this was the operator BLS key. * Update rpcevo.cpp
* Include protocol version into MNAUTH * Introduce MNAUTH_NODE_VER_VERSION = 70218
…pay#3650) It seems like the idea here was to avoid announcing already available sigshares for a signhash to everyone if concentrated recovery is enabled. But by returning there if `IsAllMembersConnectedEnabled` equals to `false` we disable the re-announcements prior to the spork activation, where we want to still have them and re-enable if the spork is enabled where we don't want to have them.
* Implement a safer version of GetCrashInfoFromException `abi::__cxa_current_exception_type()` can return `null`, handle this properly * Update src/stacktraces.cpp Co-authored-by: dustinface <[email protected]> * Update src/stacktraces.cpp Co-authored-by: dustinface <[email protected]> Co-authored-by: dustinface <[email protected]>
* Print exception origin in crash messages We use `PrintExceptionContinue` in many places and we pass crash origin to it as a param but we never use it. Also, change the param name to better match its meaning. * Update src/util.cpp Co-authored-by: dustinface <[email protected]> Co-authored-by: dustinface <[email protected]>
This was referenced Sep 8, 2020
Merged
This was referenced Sep 8, 2020
Merged
Member
Author
|
backport tag now removed from all merged PRs |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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.
I excluded a couple of PRs that didn't merge cleanly. All of these had no conflicts