Skip to content
This repository has been archived by the owner on Apr 25, 2024. It is now read-only.

Spend specific UTXO rather than all at once #54

Closed
1 of 5 tasks
sahilc0 opened this issue Apr 22, 2020 · 2 comments · Fixed by #223
Closed
1 of 5 tasks

Spend specific UTXO rather than all at once #54

sahilc0 opened this issue Apr 22, 2020 · 2 comments · Fixed by #223
Labels
enhancement New feature or request high priority prioritized, ideally for next release

Comments

@sahilc0
Copy link

sahilc0 commented Apr 22, 2020

I'm submitting a…

  • Regression (a behavior that used to work and stopped working in a new release)
  • Bug report
  • Feature request
  • Documentation issue or request
  • Support request

Expected Behavior

If user has UTXOs with 0.1, 0.7, 0.4, 0.5 BTC each - user should be able to spend 0.1 UTXO without having to spend others back as "change" to self-address

Current Behavior

Unless I'm misunderstanding, currently Caravan requires spending all UTXOs in one txn.

@waldenraines
Copy link
Contributor

If user has UTXOs with 0.1, 0.7, 0.4, 0.5 BTC each - user should be able to spend 0.1 UTXO without having to spend others back as "change" to self-address

Stay tuned 🙂.

If you're interested in this functionality you can take a look at the branch wallet-dev. But please note that this branch is very much in active development and should currently only be used with testnet coins.

@bucko13 bucko13 added the enhancement New feature or request label May 21, 2020
@bucko13
Copy link
Contributor

bucko13 commented May 21, 2020

In the latest release this is partially resolved. There still isn't support for full utxo selection, however you can select them on a per address basis when using the wallet view. This is definitely a high priority feature that we would definitely like to support very soon.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request high priority prioritized, ideally for next release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants