[bisq-network/bisq] Forced to overpay tx fees (#5662)

initCCG notifications at github.com
Sat Aug 14 14:37:38 CEST 2021

   SUPPORT REQUESTS: This is for reporting bugs in the Bisq app.
   If you have a support request, please join #support on Bisq's
   Keybase team over at https://keybase.io/team/Bisq

### Description

<!-- brief description of the bug -->
Did not find any voted proposals on minimum custom fee recently. If so, it has been arbitrarily set at 15 sat, which is too high.
Being forced to pay even 2 sats is too high for withdrawals.

Now app seems to force even new offer tx fees too high by failing offer creation with CreateMakerFeeTX error, even after funding TX already confirmed.
Then have to withdraw at 15 sat fee, and waste more sats. 

#### Version

<!-- commit id or version number -->
### Steps to reproduce

<!--if you can reliably reproduce the bug, list the steps here  -->
Create new offer to sell BTC
Fund with 2 sat tx fee from external wallet

### Expected behaviour

<!--description of the expected behavior -->
Minimum custom fee to fund or withdraw set by the user works as it did in previous versions with 2 sat minimum.

### Actual behaviour

<!-- explain what happened instead of the expected behaviour -->
Minimum tx fee errors and failed offer funding.

### Screenshots

<!--Screenshots if gui related, drag and drop to add to the issue -->

#### Device or machine

<!-- device/machine used, operating system -->

Linux Fedora 33

#### Additional info

<!-- Additional information useful for debugging (e.g. logs) -->

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210814/959a8507/attachment.htm>

More information about the bisq-github mailing list