-
Notifications
You must be signed in to change notification settings - Fork 60
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
When sending, have a max
button to send the whole balance (sweep wallet)
#546
Comments
Yes. It's something we've discussed. It's a bit intricate to make work as you change the feerate though. |
max
button to send the whole balance
yes, i think if |
max
button to send the whole balancemax
button to send the whole balance (sweep wallet)
This was brought up today again. A path forward could be to have the recovery command logic be moved to a "sweep" helper and add another command, The integration in the GUI would be more involved. If sweep was used, it should not let the user add more destinations. Nor select coins actually. @edouardparis wdyt? |
Adding the daemon label as ideally i think the sweep logic should be in the daemon and tested using the functional tests. |
Recovery panel could be renamed sweep and the primary path added to the list of recovery paths. 2 paths are accessible next block, please select one
|
That seems reasonable and pretty straightforward.
------- Original Message -------
…On Thursday, July 13th, 2023 at 2:48 PM, Édouard ***@***.***> wrote:
Recovery panel could be renamed sweep and the primary path added to the list of recovery paths.
Wording can be:
2 paths are accessible next block, please select one
- The primary path
- Signatures from Ed and Antoine can move 11 coins totalling 1.2334 BTC
- Recovery path:
- Signatures from Ed can move 4 coins totalling 0.6244 BTC
—
Reply to this email directly, [view it on GitHub](#546 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AFLK3F5SGBKKH4ZM4YTSRLDXP7VAFANCNFSM6AAAAAAYSW5S4U).
You are receiving this because you commented.Message ID: ***@***.***>
|
Do you mean to move in batch one to one or consolidate many to one? |
See also #821. |
Relevant: #863 (comment) |
Is the requirement to rename the Recovery panel as in #546 (comment) instead of adding a max button as in #546 (comment)? |
I'm not sure. Any opinion? |
I think we could do both. Having the max button on the Send page is intuitive I think and users may expect to see that option there. We could have the max button even for multiple recipients: for a given recipient, clicking the max button would return the max available for that recipient after taking into account the other recipients. |
Sounds good. Then let's do the max button first. We can track changing the recovery screen for a sweep screen into another issue. I think you have access to the beta of Liana Lite (/Online)? There is a max amount there if you want to play with it before starting with the implementation. |
46cd0f4 gui: add max checkbox for spend recipients (jp1ac4) 83fa9a9 gui: unset amount left to select if form invalid (jp1ac4) fba77a3 gui: check if feerate is already set (jp1ac4) d9b8285 gui: fix cargo fmt (jp1ac4) Pull request description: This adds the MAX button from #546. The max amount is calculated within the `redraft` function based on the change output. The recipient's amount is updated directly within this same function in order to avoid another call to `redraft` after updating the amount. The MAX button only takes effect once when the user clicks it. If further changes are made (e.g. to feerate or other recipients), the value will not update and the user will need to click MAX again. Currently, the MAX button is always clickable. It would be possible to determine for each recipient whether the MAX button should be clickable for that recipient (feerate is valid and all other recipients are valid and no duplicates), but it's not a trivial change so I'm not sure if it's worth doing as I think the behaviour is quite intuitive. ACKs for top commit: edouardparis: ACK 46cd0f4 Tree-SHA512: 16f22804d630686427da196fd1627287e2e20f2e122602c385157064323113b27b9ec9c56ada162acb55d11b8084667ee3f1a9f992a2f4eef70f25c6f7a5b20b
This is now in issue #994. |
In the send screen, it would be useful to have a
MAX
button that autofill the sum amount of all the wallet coins.The text was updated successfully, but these errors were encountered: