[bisq-network/proposals] Decentralize BSQ block explorer as we do with other Bisq infrastructure (#143)

[wiz]

> _This is a Bisq Network proposal. Please familiarize yourself with the [submission and review process](https://docs.bisq.network/proposals.html)._

Currently Bisq's [BSQ explorer](https://explorer.bisq.network/) is [run by a single operator](https://github.com/bisq-network/roles/issues/11), 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.

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.

I propose to decentralize the BSQ block explorer infrastructure in the same manner we do with btcnodes, seednodes, and pricenodes. Specifically:

- Split the current [explorer operator/maintainer role](https://github.com/bisq-network/roles/issues/11) into 1 x BSQ explorer maintainer role and 4 x BSQ explorer operator roles, similar to how we have with seednodes
- Have the BSQ explorer maintainers be @sqrrm (primary) and @wiz (backup)
- Have the BSQ explorer operators be @emzy @devinbileck @mrosseel @wiz (same as current seednode operators)
- Have each BSQ explorer run on a unique URL, i.e. explorer1.bisq.network, explorer2.bisq.network, etc.
- Change the current explorer.bisq.network DNS record into a round-robin DNS record to load balance across the 4 explorers
- 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)

Any other ideas how to improve the BSQ explorer infrastructure?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/proposals/issues/143
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191121/d10321a1/attachment.html>