Quote from: Anonymous on March 15, 2014, 06:34:34 PM

Quote from: logi on March 15, 2014, 06:32:13 PM

Quote from: Makitaki on March 15, 2014, 06:24:56 PM

Quote from: kache on March 15, 2014, 06:18:10 PM

bitember and cloudminers are on different forks, AND BOTH FORKS HAVE SAME ISSUE... Cheesy

They show the same current block 10435. The Bitember's dashboard doesn't auto refresh, hit F5 from time to time.

Might be the same block number, but bitember reports network hashrate and pool hashrate as identical, so they are on a separate fork. Any clue if cloudminers is on the proper one?

This doesn't necessarily mean a fork, I've seen similar things happen on other pools and it was due to crons fuckup or some such, wasn't actually a fork. That being said, this coin had a ton of forks before it was posted here, so I wouldn't be surprised if it started happening again.

The only forks that occurred were because of lopsided hashrate. These things don't just happen without reason. These delays are likely hashrate/difficulty related. They could be forked also.

The fork is purely hashrate related. You can't run a pool with 75% of the hashrate. Not only does it cause forks, but if it goes down the block chain stalls as the difficulty target for the next block it way too high.