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

pazza notifications at github.com
Sun Nov 28 23:52:07 CET 2021


> Watching mempool.space chugging along now I just say, it comments itself, or rather, screams a comment in favor of my proposal :)

Yes, understood. From my perspective I would like mining fees on trades to be lower. That being said I appreciate the answers provided above about the reasons this has the potential to cause issues that affects traders.

> 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).

Yes, understand the point. Anywhere the line is drawn could have the same issues.

> 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.

This could be another proposal. If accepted it could lead to a different outcome for 1 sat vb withdrawals.

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


More information about the bisq-github mailing list