<p></p>
<blockquote>
<p>There is also a <code>getbalance</code> error handling bug that needs fixing: <code>Error: null</code> is printed to the :cli console when the daemon is losing peers (<code>SOCKET_TIMEOUT</code>).</p>
</blockquote>
<p>Two solutions come to mind. When exposing this API, Bisq could:</p>
<ol>
<li>require a local bitcoin node
<ul>
<li>can be on localhost, or any IP/hostname; only requirement is that <code>peerbloomfilters=1</code></li>
</ul>
</li>
<li>use the default bitcoin nodes, but not use Tor when connecting to them
<ul>
<li>via Bisq UI: Settings > Network info > uncheck "Use Tor for Bitcoin network"</li>
<li>via Bisq command line args: <code>--useTorForBtc=false</code> (looks promising, but never tried / used it)</li>
</ul>
</li>
</ol>
<p>In both those cases, BitcoinJ would entirely bypass Tor to do basic wallet operations (calculate balance, etc).</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/issues/4198#issuecomment-627755815">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNUEBFF35UPSGF6X5ETRRIWINANCNFSM4MSDKJ6Q">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNUHVNLI3MX5Z6QFR2TRRIWINA5CNFSM4MSDKJ62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEVVMWJY.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/issues/4198#issuecomment-627755815",
"url": "https://github.com/bisq-network/bisq/issues/4198#issuecomment-627755815",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>