I would still like @JetJet13 to provide his block explorer, but given the trouble we have had keeping them up some redundancy might be in order. I have secured an agreement with @woolly_sammoth to host a B&C explorer on an going basis as well as perform block explorer maintenance and feature implementation. I know he has made progress on it in the last day. I would guess he will giving us a url and more info soon.
Thank you @woolly_sammoth and kudos to @JetJet13 for the original and ongoing work you do to provide us with a block explorer.
If Nu is even modestly successful and NuShares get up to $5 per voting block (around $1.40 now), I suspect we will see B&C Exchange completed. It is important and practical. The design is solid. It just needs funding. Right now NSR funding is what we have, so we have to get that up.
It is unfortunate the senseless and illegal Augeas default halted B&C development last year.
As mentioned above, I’ve taken a look at hosting a backup B&C blockexporer using the existing code from https://github.com/JetJet13/BCExplorer_OS. It’s currently hosted here https://bc-xplor.mj2p.co.uk although that will change in the future as that is a personal domain.
As mentioned, some of the earlier blocks are missing as the code hits an error before saving them to the database. Once I know the full extent of how many are missing I will report back here. I’ll likely write a patch script to pull the missing blocks straight from the B&C daemon rather than parsing them out of the blkindex file.
I’ve also put a bit of work into getting the various services running under supervisor which can automatically restart them if they fail (should make it a bit more stable as a block explorer) as well as covering the service with an Nginx reverse proxy. That means that the block explorer itself can be run as a non-root user which increases the security a bit. It also means I can enable HTTPS with a certificate from LetsEncrypt. I’ll feed the information on that as well as the config files back into the main project too. Just need to check over the code and write the pull request.
Yes, up and running. Recently moved to a server under Nu team control. https://bc-xplor.mj2p.co.uk.
Daemon seems stable and the block parser is working. I’m putting in work at the moment to increase the level of validation that is carried out on the parsed blockchain which should make the service more stable again and less error prone.
0 connections in your B&C daemon?
You could try connecting to the block explorer daemon. Add this line to your bcexchange.conf file
I have seen a few occasions when restarting the daemon has resulted in it not being able to make any connections. The only fix for that that worked for me was to redownload the blockchain. You could try removing the addr.dat file and restarting the daemon to see if that works?