Your comments
I anticipated the code changes for the "Overwinter" and the upcoming "Sapling" update to be hard but not _that_ hard. Fortunately I was able to solve the problem today and the pool is back.
Now it does and it is already fully compatible with the upcoming "Sapling" update.
Which of the DGB pools?
https://twitter.com/coinfoundryorg/status/1040229079801319424
Sorry for only announcing it on Twitter.
I've monitoring this for the past couple days now. It appears to have only affected our Linode based edge servers in the US and Singapore. The latter is also serving Australia. I've asked Linode support to migrate the server into a less cramped environment.
I've made some changes to the way the server calculates the hashrates. The share processing was always correct. Do guys see any improvements?
Done. We'll see if this results in the old block frequency or if there's another problem. Hopefully not something like this: https://feedback.coinfoundry.org/communities/1/topics/421-dash-situation
I will try that now.
So for both of you pinging dgb2.coinfoundry.org resolves to 138.201.116.110 - our EU server?
Customer support service by UserEcho
We've updated the coin daemons to the latest version that caused the stratums to stop. Fixed.