[bisq-network/bisq] Prevent dust outputs from being created during withdraw from wallet (#4093)

[James Cox]

@jmacxx commented on this pull request.



> @@ -629,6 +631,17 @@ public void updateItem(final WithdrawalListItem item, boolean empty) {
                     }
                 });
     }
+
+    private Coin getDust(Transaction tx) {
+        Coin dust = Coin.ZERO;
+        for (TransactionOutput txo: tx.getOutputs()) {
+            if (txo.getValue().value < 546) {
+                dust = dust.add(txo.getValue());
+                log.info("dust TXO = {}", txo.getValue().toFriendlyString());

Done:

    Mar-28 21:25:47.953 [JavaFX Application Thread] INFO  b.d.m.f.w.WithdrawalView: dust TXO = TxOut of 0.000001 BTC to msskpXKKdJdQL82zB76VRU5o5qcoXu1aYf script:DUP HASH160 PUSHDATA(20)[8790aa8150dd74fe091af8253760a23772d2e62a] EQUALVERIFY CHECKSIG 
    Mar-28 21:25:47.953 [JavaFX Application Thread] INFO  b.d.m.f.w.WithdrawalView: Dust output (100 satoshi) was detected, the dust amount has been added to the fee (was 4068, now 4168) 


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/pull/4093#discussion_r399735537
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200328/3241addf/attachment.html>