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

asvdf notifications at github.com
Sun Nov 28 11:57:12 CET 2021


Watching mempool.space chugging along now I just say, it comments itself, or rather, screams a comment in favor of my proposal :)
I understand this is minor, as trading 0.01btc and being peeved by 141sats more to withdraw is not a game changer.
I also understand the reasons behind this decision by the devs, as explained above.
I don't share the conviction that 2sat/vB vs 1sat/vB would be able to save the day in the end, I bet 2sat/vB back in april would have gotten your funds locked in mempool just as bad... so are we going to lock customizable minimum to 10sat/vB just in case that happens again? (I don't think it will, with Lightning and all)

I'd say, with the previous argumentnin mind, implementing RBF and/or CPFP in Bisq would be a way to cover for any "surprises" in the future, for the sake of safety alone. And then, it would allow to enable down to 1sat/vB.

Or (should I open another issue/proposal/question about it?) it might be a nice idea to officially resize the "FUD" about loading Bisq wallet into another wallet to manage the fees for withdrawal yourself, while reading the wiki it is multiple times unadvised to load the keys in another wallet because it might have bad consequences. Maybe compile a guideline to "load bisq wallet into external wallet, and spend from it, in a safe way, without messing anything"

-- 
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-981063919
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20211128/0b540492/attachment-0001.htm>


More information about the bisq-github mailing list