very happy to hear the revive asset process had worked in the testnet. will be nice to paste some output so the users can get familiar with the process commands needed.
in regards to the addition of testnet to the explorer proposed by @Brekyrself , it is definitely possible but will need a new server to run the testnet and the explorer backend. i think it is good to have the explorer working in the production and testnet side by side. i am not sure however if this will help knowing what witnesses are diligent, please explain me more about that.
thanks.
As far as data metrics, I was thinking just mirroring the production explorer. Witnesses should be testing the latest and greatest to make sure no block production issues arise before hitting production.
The basics such as seeing if the production witnesses are even running a node on testnet?
How many blocks they have missed?
Perhaps even blocks missed/last 24 hours?
Statistics around publishing feeds and how often?