Skip to content
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

One-Time Split UTXO for public balance #1813

Closed
kangoala opened this issue Sep 9, 2021 · 2 comments
Closed

One-Time Split UTXO for public balance #1813

kangoala opened this issue Sep 9, 2021 · 2 comments
Labels
type: Feature Request make a case for a change to a particular feature or a new feature to be added version: testnet Issue reported on a testnet version and is resolved before the next significant mainnet release
Milestone

Comments

@kangoala
Copy link

kangoala commented Sep 9, 2021

When you load up your wallet with a single public transaction, you can't publish multiple listings at once, since your single UTXO is blocked for a limited time (waiting for confirmation).

Maybe having a button which lets a single UTXO being split into several UTXOs like being done with the Private TXs in Wallet Settings would make it easier for newbies to publish multiple listings at once.

@kangoala kangoala added the New New issue logged that is waiting for acknowledgement by a responsible person label Sep 9, 2021
@zaSmilingIdiot
Copy link
Collaborator

An option to split utxos for transactions to public addresses has now been added. It defaults to 1 though (current implementation), and can be changed in the same area as the current stealth address utxo splitting option.

I do realize that this is not exactly intuitive at the moment: there's a better case to be made to use these values found in the Wallet Settings page as defaults, and have an input on the Wallet Send page available to be able to adjust it per transaction (ie: have the ability to change the split count value per transaction in the wallet send page).
This is what the actual intention is going forward. However, its not available right now, moreso as a means to avoid potential complexity in how its presented to a user that may not really understand what the control's intention/usage is, and provides some time to find a decent way to present this control. I also don't want to be adding controls in right now prior to the release, and for the most part the current change at least provides the means to adjust utxo counts, even if it is clunky for those that want to adjust per transaction.
But this can definitely be looked into and adjusted for in the next mainnet version.

@zaSmilingIdiot zaSmilingIdiot added type: Feature Request make a case for a change to a particular feature or a new feature to be added and removed New New issue logged that is waiting for acknowledgement by a responsible person labels Sep 10, 2021
@zaSmilingIdiot zaSmilingIdiot added this to the v3.0.0 milestone Sep 10, 2021
@zaSmilingIdiot zaSmilingIdiot added the version: testnet Issue reported on a testnet version and is resolved before the next significant mainnet release label Sep 16, 2021
@zaSmilingIdiot
Copy link
Collaborator

Closing: implemented (as per my previous comment) for mainnet release of v3.0.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: Feature Request make a case for a change to a particular feature or a new feature to be added version: testnet Issue reported on a testnet version and is resolved before the next significant mainnet release
Projects
None yet
Development

No branches or pull requests

2 participants