[bisq-network/proposals] Allow 1sat/vByte fee for withdrawals (#343)

[chimp1984]

> > Would it be possible to reserve the btc the moment they are attempted to be withdrawn to prevent them being used in subsequent trades?
> 
> internal wallet should definitely be able to prevent spending unconfirmed utxo's to fund new trades

That would decrease usability a lot. Much worse impace than to pay 20 cents instead of 5 cents on miner fees.

Just looked up a random tx. 5 sat is about 50 cents. So I think we are discussing nothingburgers here....
https://mempool.space/tx/e19a5fce774e8ea0566d446a067174f5a70ff5f7d9ab1e40a7fa1a09753e5f65

The problems when a trade tx gets stuck to loose weeks until the issue is clear and resolved and SPV resync is done, which can take quite some time with old and heavy wallets is far worse than to over pay a few cents. Also support costs are considerable in such times. 

Bisq has experience such events in the past when we used other (bad) fee estimation services and when fees have ben spiking fast many trade got stuck. It has been messy situation over weeks and many users got frustrated and probably left Bisq after such an experience. To make it more clear what happens:
- You are in a trade and wait days and days for the confirmation
- You start contacting support, mediation other trader but notbody can help you, you have to wait
- After about 2 weeks unconfirmed the tx is likely removed from mempools so no chance that it will ever get confirmed
- You get from support recommendation to do a SPV resync. With that the tx gets removed and the trade is a failed trade (but not lost money). The peer need to do the same. SPV resync can take hours if you have 1000s of transactions and an old wallet and CPU is 100% all that time. Not a great experience specially for non-technical users.

So thats whats at risk when we go too low...   


-- 
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/proposals/issues/343#issuecomment-954305326
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20211028/71a30ddd/attachment.htm>