[bisq-network/bisq] [v1.6.5] Change output below dust limit is burned when custom inputs are used (#5533)

Christoph Atteneder notifications at github.com
Wed May 26 11:49:39 CEST 2021


### Description

If you try to send BSQ from the wallet using custom inputs and the change output is below the dust limit, it is burnt and deducted from the senders wallet.

#### Version

v1.6.5 (probably also in older versions)

### Steps to reproduce

- Go to BSQ Wallet > Send
- Select an input (e.g. 999.94 BSQ)
- Set receiver address and amount to e.g. 995 BSQ
- Click `Send BSQ funds`

### Expected behaviour

Warning is shown that an amount below dust limit will be burnt and more inputs have to be added.

### Actual behaviour

Transactions is created and published burning the BSQ amount below the dust limit and it is displayed as Trading Fee transaction in the senders and receivers wallet.

### Screenshots

![Bildschirmfoto 2021-05-26 um 11 46 31](https://user-images.githubusercontent.com/170962/119639611-1114cb00-be18-11eb-8e2f-2c26fcbc7441.png)
![Bildschirmfoto 2021-05-26 um 11 46 38](https://user-images.githubusercontent.com/170962/119639621-1245f800-be18-11eb-9df1-e7a2597cc4eb.png)


-- 
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/issues/5533
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210526/7f851f69/attachment.htm>


More information about the bisq-github mailing list