-
Notifications
You must be signed in to change notification settings - Fork 40
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
No fee input added if deductFee is set to false and tx amount matches an account utxo #133
Comments
@Alex-Werner are we tracking this bug to be fixed in one of the upcoming releases or shall we bounty it out to the incubator? |
It is tracked, it is groomed, and it is planned ready for being work on. Our way to "fix" that situation is by explaining to the user within broadcastTransaction in a min fee check that it won't be broadcastable. |
Discussed in Triage - P1, Maverick to discuss with Alex. |
It's closed. Please reopen in case you notice anything suspicious. |
Please retest |
currently getting
|
@Alex-Werner please refer |
retest failed:
|
What in fact is the purpose of deduct_fee flag in that case? |
Consider a tx with the option
deductFee: false
and an amount of e.g.2e6
:If the account has an UTXO with
2e6
the default strategy will select that sole input, apparently unaware of thedeductFee: false
option. As a result:is thrown since no additional input is added to cover the fee.
The text was updated successfully, but these errors were encountered: