<blockquote>
<p><em>This is a Bisq Network proposal. Please familiarize yourself with the <a href="https://docs.bisq.network/proposals.html" rel="nofollow">submission and review process</a>.</em></p>
</blockquote>
<p>Currently Bisq's <a href="https://explorer.bisq.network/" rel="nofollow">BSQ explorer</a> is <a href="https://github.com/bisq-network/roles/issues/11" data-hovercard-type="issue" data-hovercard-url="/bisq-network/roles/issues/11/hovercard">run by a single operator</a>, and it usually works fine. However, like any centralized service running on a single server, it occasionally has issues, such as being out of sync with the network, or simply being offline or unavailable.</p>
<p>Usually when you encounter a malfunctioning block explorer, you can just use a different block explorer, but with BSQ there is only one, so the options are very limited. This is clearly a CPOF of Bisq infrastructure, and we should have more than a single BSQ explorer.</p>
<p>I propose to decentralize the BSQ block explorer infrastructure in the same manner we do with btcnodes, seednodes, and pricenodes. Specifically:</p>
<ul>
<li>Split the current <a href="https://github.com/bisq-network/roles/issues/11" data-hovercard-type="issue" data-hovercard-url="/bisq-network/roles/issues/11/hovercard">explorer operator/maintainer role</a> into 1 x BSQ explorer maintainer role and 4 x BSQ explorer operator roles, similar to how we have with seednodes</li>
<li>Have the BSQ explorer maintainers be <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/sqrrm/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/sqrrm">@sqrrm</a> (primary) and <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/wiz/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/wiz">@wiz</a> (backup)</li>
<li>Have the BSQ explorer operators be <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/Emzy/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/Emzy">@Emzy</a> <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/devinbileck/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/devinbileck">@devinbileck</a> <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/mrosseel/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/mrosseel">@mrosseel</a> <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/wiz/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/wiz">@wiz</a> (same as current seednode operators)</li>
<li>Have each BSQ explorer run on a unique URL, i.e. explorer1.bisq.network, explorer2.bisq.network, etc.</li>
<li>Change the current explorer.bisq.network DNS record into a round-robin DNS record to load balance across the 4 explorers</li>
<li>Add a user preference into Bisq which allow users to choose which BSQ explorer to use, similar to how users can currently select a Bitcoin block explorer (with the round-robin as the default)</li>
</ul>
<p>Any other ideas how to improve the BSQ explorer infrastructure?</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/proposals/issues/143?email_source=notifications&email_token=AJFFTNSPB56F7B2TJQZ3YQLQU4DBTA5CNFSM4JQI7GAKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H3HPRVQ">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNRA3RXPKR2XBTMZ3ELQU4DBTANCNFSM4JQI7GAA">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNS5ODO7B3SPNFE2BM3QU4DBTA5CNFSM4JQI7GAKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H3HPRVQ.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/proposals/issues/143?email_source=notifications\u0026email_token=AJFFTNSPB56F7B2TJQZ3YQLQU4DBTA5CNFSM4JQI7GAKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H3HPRVQ",
"url": "https://github.com/bisq-network/proposals/issues/143?email_source=notifications\u0026email_token=AJFFTNSPB56F7B2TJQZ3YQLQU4DBTA5CNFSM4JQI7GAKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H3HPRVQ",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>