Looking at the history of the other community nodes in the current epoch (3269), I found only two that have a VoteCount value above 0. 2 out of 80. [EDIT: Nope, not out of the full 80. See post below.] That many community pNodes and vNodes can’t be misconfigured, sitting on poor internet connections, etc. That’s an abysmal rate.
Comparing one of those Nodes against mine posted above, I can see that more of the shards have been synced. Yet this Node looks to have finished up Epoch 3227, then stopped syncing a day later around Epoch 3232. As a result, it too is now reporting a VoteCount of 0.
I’m just trying to understand the sync status of Nodes, as the blockchain actually sees them since this will form the base factor for (the upcoming) slashing. As @doc and others have noted the past few months, as a community we’re concerned that our Nodes may not be performing correctly. These Nodes have been online and earning for 18 months without the proper technical feedback to diagnose the actual consensus performance.
For vNode operators, they will be able to resolve issues once definitively identified and instructions posted, since they have the necessary access to make configuration changes.
For pNode operators, they are at the mercy of the devs and/or support team. Other than supplying power and an internet connection, there isn’t much more a pNode operator can do to resolve technical and/or configuration problems. pNode operators don’t have ready access to the terminal without partial physical disassembly of the pNode. And even if they did – many operate pNodes so they don’t have to (re)configure docker or edit run.sh.
