Done.

You were right Pavel. Someting was indeed wrong. Upon inspecting the logs I've discovered that both Verge pools actually found a couple blocks throughout the night which were rejected by the daemon. I've updated the pool code to prevent this from happening for future blocks. I'm pretty confident that the problem has been identified. The pool has mistaken the coin as a proof-of-work coin when in fact mining requires to pool to operate in proof-of-state / proof-of-work hybrid mode.

I've spent the entire day fixing the pool code which was quite difficult given that there's no real documentation or example pool code for Verge.

Sure, no problem. Although I doubt that the daemon restart was responsible for the recent Dash blocks. If you page through the Dash Pool's block history, you'll find extra long rounds every now and then.

Which of the XVG pools lyra or blake?

Yeah we've had (and apparently still have) our share of problems with the accuracy of the displayed hashrates vs. what miners report locally. The code in question is open-source: https://github.com/coinfoundry/miningcore/blob/master/src/MiningCore/Mining/StatsRecorder.cs#L131

The code has been peer-reviewed by quite a few developers. But still, if you have a programming background and spot any inaccuracies with the calculations, feel free to submit a PR.

I have to correct myself here. Upon inspecting the logs I've discovered that both Verge pools actually found a couple blocks throughout the night which were rejected by the daemon. I've updated the pool code to prevent this from happening for future blocks. Verge is quite tricky as there's absolutely zero public examples of working code for this currency.

xvg2.log:[2018-02-18 10:50:22.7585] [W] [xvg2] [Bitcoin Job Manager] Block 1890032 submission failed with: Unable to sign block, wallet locked? 

And no, the wallet was not locked.

Update: I'm pretty confident that the problem has been identified. The pool has mistaken the coin as a proof-of-work coin when in fact mining requires to pool to operate in proof-of-state / proof-of-work hybrid mode.

We have had long rounds in the past. I've just restarted the dash daemons to be sure there's not a problem with the dash-nodes.

I'm talking about the pool not finding blocks during that period. Feel free to inspect the pool's wallet on the blockchain explorer. It's directly linked on every pool's page.

Thanks. I'll try to figure out how that happened.

/thumbs up :-)