-
Notifications
You must be signed in to change notification settings - Fork 37.7k
gui: Add a Make unsigned
button next to Send
#18656
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
Conversation
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. ConflictsReviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first. |
2474e98
to
5f80564
Compare
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.
Concept ACK.
Instead of changing Send to make an unsigned tx for wallets with private keys disabled, have a separate button for that functionality and disable Send for such wallets.
5f80564
to
0acaefa
Compare
This would likely confuse users as-is. Can we simplify the workflow so it always makes a PSBT, but in a way that users can easily sign+broadcast? Perhaps the PSBT dialog can become like the current send confirmation dialog unless an expert-mode option is enabled? |
I think sticking this behind an expert mode switch is probably the right thing to do at a minimum. |
Instead of having the Send button mutate into a Create Unsigned button when
IsWalletFlagSet(WALLET_FLAG_DISABLE_PRIVATE_KEYS)
, have a second button that always creates a psbt. The original Send button will then not change its behavior and just disable itself when private keys are disabled.#17509 does a refactor that makes this easier, so this PR is dependent on that.
Split from #18627