Fixes #810.
Not much to explain; we were requiring the wallet to be unlocked for the unsigned transaction creation process. Fix this by moving the unlock wallet request to the signed transaction creation process.
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
See the guideline for information on the review process.
Type | Reviewers |
---|---|
ACK | pablomartin4btc, hebasto |
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.
Concept ACK
I’ll test it soon.
tack 671b7a32516d62e1e79393ded4b45910bd08010a
Send
prompts the passphrase, Create Unsigned
does not prompt the passphrase
542@@ -549,10 +543,15 @@ bool WalletModel::bumpFee(uint256 hash, uint256& new_hash)
543 DataStream ssTx{};
544 ssTx << psbtx;
545 GUIUtil::setClipboard(EncodeBase64(ssTx.str()).c_str());
546- Q_EMIT message(tr("PSBT copied"), tr("Copied to clipboard", "Fee-bump PSBT saved"), CClientUIInterface::MSG_INFORMATION);
547+ Q_EMIT message(tr("PSBT copied"), tr("Fee-bump PSBT copied to clipboard"), CClientUIInterface::MSG_INFORMATION | CClientUIInterface::MODAL);
At least on Ubuntu 22.04, now after the fee-bumping unsigned a modal pop-up is displayed:
while before there was a message sent thru the OS system information (?):
I see in the code we usually use CClientUIInterface::MSG_INFORMATION
(transactionview.cpp
, walletview.cpp
) and I’d prefer to keep this look & feel but at the same time I think having the modal window popping up it’s making the user more aware of what just happened with the intention to accept it.
tACK 671b7a32516d62e1e79393ded4b45910bd08010a
Tested and verified this PR fixes #810 and now creation of unsigned tx/ PSBT/ during fee-bumping doesn’t ask for passphrase/ requires wallet unlock.