Change should greater than dust when alwaysChange#135
Change should greater than dust when alwaysChange#135akashiceth wants to merge 1 commit intopaulmillr:mainfrom
Conversation
|
Could you add some tests? |
Tests added, but the GitHub Action failed. However all tests passed on my local side when I run |
|
Hmm why can't you simply use alwaysChange: false? |
One of our use cases is: Three parties partially sign a PSBT. Two of the parties partially sign their own inputs and outputs, while the last party verifies them, pays the fees, and submits the transaction. When alwaysChange is set to false, the first two parties will not change outputs that are smaller than the dust; instead, they will use this intended change to pay the transaction fees. The "alwaysChange" here isn't quite as "always" as it claims—it fails to change when the output is less than dust. |
|
The current behavior works properly for ordinals. It wouldn't work if this is changed. Your use case is nevertheless valid. I think the new feature should be under the new flag. Do you have a naming idea? |
Change smaller than dust is meaningless. When
alwaysChange: true, the change should be greater than dust.The example above will change 67 sat, but it would be better to change 5067 sat