[BUG][GUI] Refine bytes/fee/"after fee" calculation in coin-control #2568
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Should close #2156
This bug is caused by the fact that a transparent input is usally 148 bytes (149 for p2cs spends), but can also be 149 sometimes (150 for p2cs spends), depending on the script length.
When a user copies "After fee" in coin-control, and sends it to a single recipient, this extra fee is typically (with few coins selected) offset by the lack of change output. But, when many inputs are selected in coin control, this becomes relevant.
Also:
CTXIN_SPEND_DUST_SIZEandCTXOUT_REGULAR_SIZEinsapling_operation.h