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

[cd2357]

There were periods when the min fee was 1sat/vB and when the mempool filled up for a few weeks, it caused countless issues with failed trades, DAO voting, BSQ compensation, support tickets, etc. People complaining
- "Bisq is broken, has too many bugs, it should just work"
- "My trade is hanging, I want my money back"
- "My trade failed, I want my fees back"

Many of us have spent a lot of time to optimize and minimize the mining fees (and overall trading fees) where possible:
- switched from earn.com to mempool.space fee estimation
- ongoing efforts to reduce trading protocol from 3 on-chain to 1 on-chain transactions
- year-long efforts, backed by generous donors, to fund custom dev work to fully enable segwit
- tweaking of fee estimation at different stages of the trade protocol, to ensure trade is reliable, but to not overpay
- and countless more

So it is an ongoing balancing act. Its not just "devs go find the line, edit, save, done".

My personal opinion: before asking for a code change, it might be worth it to first look for easier / more profitable / less disruptive ways to make up for the 1 sat/vB difference in withdrawal mining fees:
- for all your trades, pay the trading fees in BSQ instead of BTC (about 50% savings)
- become a market maker, instead of a taker (those who create offers pay much smaller trading fees)
- try to create trade offers when the mempool is free (lower estimated mining fees for both trade participants)
- instead of many trades with small amounts, go for fewer trades with higher amounts



-- 
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-954569703
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20211029/68a677f9/attachment.htm>