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

[Chris Beams]

>     * Have each BSQ explorer run on a unique URL, i.e. explorer1.bisq.network, explorer2.bisq.network, etc.

+1 to each explorer running at a unique URL, but from a decentralization perspective, I'd prefer to go with the current scheme, where the operator hosts it under one of their own domains, e.g. as @sqrrm has done with https://explorer.sqrrm.net. It should have some value for the user to see these (i.e. in the list of available explorers), as they'll naturally intuit that these instances are run by individual Bisq contributors. This will have the same effect as seeing the list of seednodes in Bitcoin Core's `chainparams.cpp`, e.g. `seed.bitcoin.sipa.be`, `seed.bitcoin.jonasschnelli.ch`, etc. On the contrary, if all hosts were subdomains under `bisq.network`, e.g. `explorer1`, `explorer2`, the user would get the sense that some kind of more traditional centralized entity is operating them.

>     - Change the current explorer.bisq.network DNS record into a round-robin DNS record to load balance across the 4 explorers

I've noticed that the two current explorer instances at https://explorer.sqrrm.net and https://explorer.bisq.network can have slightly different data on the main ("Recent") page. At time of this writing they are in sync, but a few minutes prior, one of them had a handful of recent transactions that the other didn't. If the round-robin approach naively load balanced across these instances, the user could have a confusing experience of data appearing and disappearing as they click and/or refresh. Session affinity should solve this, and while implementing it is probably a given, it's perhaps still worth raising awareness about and adding to the requirements explicitly.



-- 
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#issuecomment-561366153
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191203/7c8e7396/attachment.html>