Closed NicolasDorier closed 10 months ago
How can we differentiate the cases;
If we can differentiate the second case, user can try to send it again after fees dropped. When the fees are lower, subtracted amount will be less and remaining amount could be bigger than dust.
But the first case will be always fail.
Right now both of them throws OutputTooSmallException
exception, so no way to handle them differently
While it shouldn't really matter economically speaking to remove output with a value that is too small, it is surprising behavior for users, and give rise to several edge case.
Assuming 540 of dust, here is a summary of the changes of behavior:
Before, we would silently remove such outputs in the built transaction. Now the builder will always throw an exception.