Quote from: Mister1k on November 11, 2014, 03:08:17 PM

Quote from: cryptonit on November 11, 2014, 02:41:43 PM

Quote from: miningfield on November 11, 2014, 02:35:08 PM

US miningfield pool was never attacked, when the pool was beeing managed by utah john it went offline several times because of host problems, (he was mining on the host that had the VM with the pool, wich got unstable)

This issue with the chain didn't got resolved by itself on the US Pool because i was missing the bantime=600 on the config, when it forked it banned the correct peers for 24h instead of 10m, if it reconnected to the correct peers after 10m it would eventually correct to the right fork.

I did restored the chain to try and get the pool on the correct fork faster.

thx for clarify

bantime=600 is required for selfhealing
else u refuse to speak with wallets on correct chain
and cant find out that u are following the dark side of force.......

So it didn't selfheal. Did it!
It forked and then because of the missing parameter it could'nt self heal. Ok but the missing parameter didn't cause it to fork.did it?.
and your wallet was affected how?
Is it time for another picture because you can't answer the question. Maybe pallas can dig up a pic for you.

forks can happen for a number of reasons, not necessarily an attack.
you are calling for funny pictures so we deliver.