Quote from: Profit Hunters Club on January 20, 2018, 10:34:04 PM

Quote from: MadPool on January 20, 2018, 09:32:32 PM

Quote from: canonical on January 20, 2018, 09:19:19 PM

Quote from: canonical on January 20, 2018, 09:13:34 PM

Quote

Madpool is at the correct chain again! Grin

No need to worry: We will get in touch with the developer team to compensate the 37 blocks to our miners which are orphan now because of the incorrect chain!

MadPool looks to be behind again.

MadPool is on it's own chain again. It's mining every block.

yes, just resynced. Madpool is back on the main chain again. Anyone has an idea how to prevent that in the future?
Maybe we should call it "Chain Hunters" Cheesy

There are several reasons for you to fork onto your own chain:
- A spike in hashpower will get your pool banned by other nodes on the network, if stratum remains connected to your wallet while your chain falls behind it will begin building its own chain without your wallet automatically resyncing to the main network.
- Core 8 has issues trying to deal with chain-forks, this will not be an issue (if your pool is not trying to go above 51%) once PHC can be upgraded to Core 10 (hopefully in the near future)

Multi-pool operator suggestions:
- Turn off the auto-coin switching feature for PHC so your pool hashrate is more stable and the other peers on the network "learn" the average correctly.
- Have a script verify blockheights from a block explorer.

"A spike in hashpower will get your pool banned by other nodes on the network"

How sensitive is this? If someone with, say, 10Gh decided they wanted to mine PHC and joined the pool, are you saying that, just the act of joining the pool will bring down the pool?