Reevaluating 'Dust' Considerations When Adding Change in Transactions about coinselect HOT 5 OPEN

I've given you write access to this repo if you'd like to work on it.

from coinselect.

Regarding dust, it's important to understand that the UTXO coin selection algorithms in this repository do not add change outputs if they are below a dust threshold. However, users bear the responsibility to ensure that their target outputs do not fall into the 'dust' category, which is crucial for preventing the creation of transactions that might not be relayed by Bitcoin nodes, depending on their policies. Also, it's noteworthy that the dust metric used here differs from the one employed in Bitcoin Core (see message above).

For illustration, consider this test case, where the output value (1) is below the 546 satoshi dust threshold for P2PKH outputs:

As this repository focuses on non-SegWit transactions, a straightforward measure to ensure compliance with dust policies could be to verify that all target values are at least 546 satoshis. This threshold assumes the Bitcoin Core default dustRelayFee of 3000 satoshis per kilobyte.

Note: This issue does not address a bug, but rather proposes an idea for potential future consideration and improvement.

from coinselect.

I've given you write access to this repo if you'd like to work on it.

Thanks! I've been deeply engaged in developing a coinselect repository that leverages descriptors, and my work is heavily influenced by this repository. That's why I've been looking so closely into it.

Once I finish up with my current work, I plan to come back and make some basic changes here too, especially to align the dust calculation with Bitcoin Core and to prevent creating targets that might not get relayed.

Looking forward to contributing more soon.

from coinselect.

Feel free to make a breaking release. This repo is outdated in many ways. Just let me know when you want a version published (you can tag it on Github first and I'll just publish those)

from coinselect.

Hello everyone, are there any updates on this? @landabaso, have you had a chance to work on the issue?

from coinselect.