Quote from: crowetic on September 26, 2016, 10:54:25 PM

There are some fixes in place temporarily that seem to have ceased the forking issues that we were seeing.

The wallets do sometimes though, under heavy load, get 'stuck' and require a restart.

We are building new pool software to sort this issue out. But the forking should have been solved a few weeks back, I don't think any of the pools have actually forked since this fix was applied.

I was very busy the last few days, so the sole responsibility was on haitch to handle any pool issues, and for a time there, there weren't any.

I also know that he DOES have emails setup to go off when a pool is having an issue, or marked as 'forked' by the monitor. So that's already there, the only issue is that there are only two of us with access to ninja's root, and so it's on one of us to handle the issues when they arise. I myself was like I said very busy, so it was on solely haitch. If it hadn't been for him fixing the issues, they'd have been happening even longer.

The new pool software should be finished fairly soon, and I believe it is undergoing live testing as we speak. This will distribute the load on the wallets, and help out with the stalling issues we've been seeing, even after the fork issues were handled.

Thanks!

I've got more news, but I'll likely be posting that in a day or two, still catching up from the long family weekend. Hope all is well!

Ya, seems the dev v2 pool is also stuck/forked... Is pool software the root cause? Or does this forking issue lie within the Burst protocol? I would think developing/updating "new pool software" as a work-around for a deeper issue is the wrong approach to take here, especially since most pool miners would then be incentivised to mine on said pool, which doesn't help at all with decentralization.