<p></p>
<blockquote>
<p>This change would be the lowest-risk, because it's just swapping out one API for another.</p>
</blockquote>
<p>Replacing earn.com with another TTP / CPOF is not an acceptable solution IMO. If we wanted to do that we could simply query the mempool.space API at <a href="https://mempool.space/api/v1/fees/recommended" rel="nofollow">https://mempool.space/api/v1/fees/recommended</a> which is the same as <a href="https://bitcoinfees.earn.com/api/v1/fees/recommended" rel="nofollow">https://bitcoinfees.earn.com/api/v1/fees/recommended</a> but this would just make everyone trust my node, which is why I'm proposing that all pricenodes run their own open-source backends for local fee estimation in the spirit of decentralization. AFAIK all pricenode operators already operate bitcoin nodes, so this is very easy to arrange.</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-623641645">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNRYFFKQQK3SDXJLKHTRP4FJZANCNFSM4LGEVL3Q">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNUO54JMAJN3DFF5FDLRP4FJZA5CNFSM4LGEVL32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEUWAILI.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-623641645",
"url": "https://github.com/bisq-network/projects/issues/27#issuecomment-623641645",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>