You are viewing a single comment's thread:
This is exactly the reason why I'm all the way down in the 70s rank. :D While I do understand code, I can't for the life of me get my head around C++ which hive is developed in so I certainly can't help nor validate code directly other than asking opinions of more informed people and reading changelogs and other explanation and discissions.
A lot of new people who have become witnesses generally go out of their way to ask questions and ask what's the recommended setup and tools I should use. They'll get pointed to various price feed scrips, hive witness essentials, and other documentation and usually they get up and running quickly and run mostly flawlessly.
It's unacceptable in any degree to have a witness miss blocks for an extended period of time. Disabling a witness is the EASIEST thing you can do. It can be done on peakD, ausbit's website, via CLI, via custom scripts, via witness essentials witness watcher.
I have custom node scripts I can run with will disable all the witnesses I manage if there is ever a need I also run witness watcher on an external VM as well.
It's not difficult. it take no time at all to set up.. There is absolutely no reason what so ever that leofinance could come up with to excuse them of this negligent failure.
And this isn't the FIRST time this has happened with leofinance either.
Well I made the same mistake that these guys made... I lost somedays trying to figure out the problem and didn't deactivated the witness, I only did that after a while...lesson learned! The important is not to repeat the same mistake I guess :P
Yeah... but no. There are a few "details" that are different between these two cases:
While it's not cool to miss blocks, you are not even in top50 and nobody expects you to run full blown witness infrastructure with monitoring, backups, public seed node, etc.
View more