My 2 cents: There should only be a rollback if its necessary to fix a technical problem that caused this. You can talk about fairness until you are blue in the face but I think some of the blame here is misguided; If you mined for 2 days on the wrong fork, the pool is the one at fault, not the Magi developer. It was obvious on Sunday at Zpool that something was not right when it was finding almost every block. If it sounds too good to be true, it probably is. Same goes with Suprnova. When you mine through a pool you are taking a risk that you won't get paid, your hashrate isn't correct, etc. Zpool and Suprnova continued to have high hashrates all day yesterday when it was completely obvious they were on the wrong chain. Unfortunately I think the human nature of greed took over and everyone starting mining there because the returns were insane. It seems like a lot of other complaints on here are dealing with payments from those pools.
I'm not an expert but it seemed pretty obvious what to do yesterday if you wanted to mine: Use a pool that was on the correct fork, and make sure your wallet is on the correct fork.
https://poolinfo.systms.org/ pretty much showed that PoM was the only pool operating on the correct fork. It was no surprise that I was able to mine on it all yesterday and receive my earnings with zero issues. My wallet wasn't syncing past a certain block so I followed the simple solution that was posted here numerous times to put the connect command into my conf file. Problem solved. It also blows my mind that people were trying to send coins to Bittrex when they were having known problems. In my humble opinion, most people mining to these pools with extreme returns were either burying their heads in the sand or were engaging in pure speculation.
The main issue though with a rollback though is what happens if this happens again? Another rollback? Its a slippery slope to go down, especially when you try to determine what is "fair."
