<p></p>
<blockquote>
<p>As far as I'm aware, users haven't been complaining about the tx fee rate in Bisq except during a couple incidents where rates were way too high and got stuck there. This happened in 2017, just recently, and IIRC there was one other time too.</p>
</blockquote>
<p>That is a rather charitable interpretation I'd say, considering that</p>
<ul>
<li>people only realize what mining fees they pay if they read the fine print in the trade popup</li>
<li>of those who do, few know what an acceptable mining fee is at the moment of the trade</li>
<li>of those who know, few get upset enough to want to report it</li>
<li>of those who want to report it, few know exactly how to do it</li>
<li>of those, even fewer have the patience and willingness to setup keybase, or setup a github account + create an issue</li>
</ul>
<p>So there are many stages to go through, and only the last group are "visible" to the Bisq team as having made a complaint.</p>
<p>Its also a question of which metric to use when deciding how to prioritize limited dev resources:</p>
<ul>
<li>minimize amount of BTC unnecessarily "lost" by traders in every trade?
<ul>
<li>then prioritize fee estimation (done), bech32 support (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="285254817" data-permission-text="Title is private" data-url="https://github.com/bisq-network/bisq/issues/1139" data-hovercard-type="issue" data-hovercard-url="/bisq-network/bisq/issues/1139/hovercard" href="https://github.com/bisq-network/bisq/issues/1139">#1139</a>) + upgrade BitcoinJ (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="436333065" data-permission-text="Title is private" data-url="https://github.com/bisq-network/bisq/issues/2772" data-hovercard-type="pull_request" data-hovercard-url="/bisq-network/bisq/pull/2772/hovercard" href="https://github.com/bisq-network/bisq/pull/2772">#2772</a>), possibly RBF (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="280762188" data-permission-text="Title is private" data-url="https://github.com/bisq-network/bisq/issues/1077" data-hovercard-type="issue" data-hovercard-url="/bisq-network/bisq/issues/1077/hovercard?comment_id=357526156&comment_type=issue_comment" href="https://github.com/bisq-network/bisq/issues/1077#issuecomment-357526156">#1077 (comment)</a>), etc</li>
</ul>
</li>
<li>minimize amount of open tickets and complaints?
<ul>
<li>then prioritize those things which most amount of people complain about</li>
</ul>
</li>
</ul>
<blockquote>
<p>With the above said, I don't see this as a priority now that we've solved the problem of too-high fee rate recommendations out of earn.com with <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/cd2357/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/cd2357">@cd2357</a>'s PR at <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="579705286" data-permission-text="Title is private" data-url="https://github.com/bisq-network/projects/issues/27" data-hovercard-type="issue" data-hovercard-url="/bisq-network/projects/issues/27/hovercard" href="https://github.com/bisq-network/projects/issues/27">bisq-network/projects#27</a>.</p>
</blockquote>
<p>I agree with <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/cbeams/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/cbeams">@cbeams</a>. From a <em>"should Bisq merge this change"</em> perspective, this PR is probably not necessary anymore, now that the fee estimation is more accurate. So I'll just go ahead and close the PR.</p>
<p>However, looking from a <em>"should Bisq eventually support this"</em> sort of perspective, I'd say yes. After all, Bisq is open source and if the protocol allows such a change, sooner or later someone will patch their local client and do it, cause it would be in their best interest to save some sats on mining fees.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/bisq-network/bisq/pull/4231#issuecomment-625642486">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNWG2REOFQXPPLXO7YDRQOL7JANCNFSM4MYKX6HA">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNQGOCFSRB4CD5QV27LRQOL7JA5CNFSM4MYKX6HKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEVFIX5Q.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/bisq/pull/4231#issuecomment-625642486",
"url": "https://github.com/bisq-network/bisq/pull/4231#issuecomment-625642486",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>