Closed cbeams closed 4 years ago
@sqrrm @KanoczTomas : Would you be ok to take over the BSQ explorer role after the DAO launch? We should have 2 explorers running for resilience.
Yeah, I'm good to run one explorer instance. Would be great if someone with some web dev experience could take over the development though.
@KanoczTomas From what I understand you have some more experience on the operations side so you're probably better situated to improve on the stability of running the explorers. I'm already running one and if you run the other we should get together to figure out what we can do to make them better.
@ManfredKarrer yes, I am ok with running a second instance.
@sqrrm it would be perhaps interesting to somehow move the BSQ explorer to esplora if the current one has problems with developement. Esplora uses electrs in the background, so maybe if bisq dao created a json in the format as electrs returns it would be a way to go. It if just a thought for now. Would require more analysis of the code.
I will create a vm and contact you how to proceed @sqrrm .
@KanoczTomas Yes basically that would be good but will require more work to see what is needed. After the DAO launch we can look into it.
Started as explorer operator/maintainer. I'm running one node for betanet right now at explorer.sqrrm.net/betanet
Will move that over to mainnet when we go live, which shouln't be much of a problem as betanet is already on mainnet but with test BSQ.
I will take over the role from april 1. I had no time to setup the 2nd node yet, as planned. Will do in the coming days.
I've been running an explorer, both clearnet and onion on https://explorer.sqrrm.net/ and murt7p2srbvorslyhud2rvvg2dkjpmtmku5p67lms72hqmuauibbisqd.onion respectively.
There has been no issues with the setup during the first cycle. I don't even think I've restarted the seednode once. I plan on moving this to explorer2.bisq.network or something like that as well.
@sqrrm Takes over primary role owner
I have taken over primary role owner. I'm also managing both explorers. The explorers have been running without problem but they're rather primitive. It would be good to get someone to take over this role and the management of the explorers.
Running two explorers
https://explorer.bisq.network/ https://explorer.sqrrm.net/
There was quite a lot of trouble with the explorer nodes this cycle. I think the seed nodes are not stable when dumping DAO data to disk and the monitor then reads it. It would probably be better if there was an api for the explorer to get the data from the seed node.
It's also really slow to parse from genesis, each block taking up to 20s, that needs to be investigated.
Running two explorers
https://explorer.bisq.network/ https://explorer.sqrrm.net/
Fixed quite a few issues with the explorers, they're now running smoother but still require quite a lot of attention.
bisq-network/compensation#325
Running two explorers
https://explorer.bisq.network/ https://explorer.sqrrm.net/
There are some issues with the explorer, would need more time to look at it. Main issue has still been the stability of the seed nodes but seems to be better with the latest version.
Running two explorers
https://explorer.bisq.network/ https://explorer.sqrrm.net/
Explorers have been needing restart a few times, although it's possible they would've recovered with the automatic restart.
Running two explorers
https://explorer.bisq.network/ https://explorer.sqrrm.net/
There are some issues after the latest upgrade so explorer.bisq.network is still running a seednode on 1.1.6
Running two explorers
https://explorer.bisq.network/ https://explorer.sqrrm.net/
Running ok now. Bitcoind crashed once.
bisq-network/compensation#441
I have moved to running only bsq.sqrrm.net. Costs are up as it's a vps with large ssd rather than a hd.
Also ran two explorers https://explorer.bisq.network/ https://explorer.sqrrm.net/ that will soon be decommissioned
There are now 6 explorers run by @wiz @sqrrm @devinbileck @mrosseel @Emzy @m52go
bisq-network/compensation#461
Setup of one explorer
Running one explorer https://bsq.emzy.de/
/cc bisq-network/compensation#467
Cycle 9 report
/cc bisq-network/compensation#468
I have setup and am now running a BSQ explorer.
https://github.com/bisq-network/bisq/pull/3861
Total: 120 USD
Running one instance at bsq.sqrrm.net, had one issue with the seednode getting in conflict with the DAO state. Don't know why, and it looks like some other seed nodes had the same issue.
bisq-network/compensation#488
@wiz, please update https://github.com/orgs/bisq-network/teams/explorer-maintainers/members and the description of this issue to reflect the actual set of BSQ explorer operators, thanks.
@wiz, please update https://github.com/orgs/bisq-network/teams/explorer-maintainers/members and the description of this issue to reflect the actual set of BSQ explorer operators, thanks.
Sorry, scratch the first part of that request. I was confusing the @bisq-network/bsq-explorer-maintainers group with the @bisq-network/bsq-explorer-operators team. These roles need to be separated out, I'm doing that now.
Ok, I've just separated out the BSQ explorer operator and maintainer roles. This role represents the operator role and has been renamed accordingly. @sqrrm has agreed to own the maintainer role, and #103 has been created to reflect.
@wiz, please paste a definitive list here of which operator operates which instance and I'll update the description accordingly.
I've already updated the assignee list. @bisq-network/bsq-explorer-operators, please continue to issue your cycle reports here, thanks.
bsq.ninja (@wiz)
bsq.sqrrm.net (@sqrrm)
bsq.bisq.services (@devinbileck)
bsq.vante.me (@mrosseel)
bsq.emzy.de (@emzy)
bsq.bisq.cc (@m52go)
Running one instance at https://bsq.sqrrm.net, no issues.
bisq-network/compensation#536
Running 1 instance at https://bsq.bisq.services/. I recently increased disk size to 400GB since it was close to getting full.
https://bsq.ninja/ running stable with latest patches
Running 1 instance at https://bsq.bisq.services/. Increased TMPFS allocation for growing datastore, see https://github.com/bisq-network/bisq/pull/4246.
/cc bisq-network/compensation#562
Increased TMPFS allocation for growing datastore, see bisq-network/bisq#4246.
/cc bisq-network/compensation#570
Running one instance at https://bsq.sqrrm.net, no issues.
bisq-network/compensation#564
Running 1 instance at https://bsq.bisq.services/. Nothing to report.
Nothing to report.
/cc bisq-network/compensation#595
Running one instance at https://bsq.sqrrm.net. Had some issues and had to upgrade to latest seed node, which turned out to be quite painful as the scripts had changed the name of the seed node service. Now running ok
bisq-network/compensation#597
/cc bisq-network/compensation#601
https://bsq.ninja/ is running stable
https://bsq.bisq.cc has been running better with the increased tmpfs allocation but still seems to lag occasionally.
/cc bisq-network/compensation#615
Running one explorer https://bsq.emzy.de/
redirects now to mempool.emzy.de/bisq
/cc bisq-network/compensation#617
1 explorer in operation, been current since fixing some stuff last month. Looking forward to moving to the mempool explorer
This role is responsible for operating an instance of the BSQ explorer webapp. See also the BSQ Explorer Maintainer role at #103.
Docs: TBD Team: @bisq-network/bsq-explorer-operators
Instances and their operators: