<p></p>
<blockquote>
<p>If my understanding is correct, all Bisq nodes have access to Bitcoin Core (either to a local node, or through a service interface exposed by a full node).</p>
<p>In that case, why not just use Bitcoin Core's mechanism for fee estimation? They already expose it through their API: <a href="https://bitcoin.org/en/developer-reference#estimatesmartfee" rel="nofollow">estimatesmartfee</a>.</p>
</blockquote>
<p>Bisq nodes are connected to one or more Bitcoin Core nodes via the Bitcoin p2p protocol. They have no access to these nodes' RPC interfaces, and <code>estimatesmartfee</code> is an RPC. It would be possible to give Bisq access to one's own personal Bitcoin Core node's RPC API, but it would not be a general, works-out-of-the-box solution for all Bisq users.</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/projects/issues/27#issuecomment-623111100">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNXLDDUBPSB6DTDCM5LRPVXDRANCNFSM4LGEVL3Q">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNS56DTTN4XLK23ESC3RPVXDRA5CNFSM4LGEVL32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEUR6XPA.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/projects/issues/27#issuecomment-623111100",
"url": "https://github.com/bisq-network/projects/issues/27#issuecomment-623111100",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>