Quote from: Mister1k on November 11, 2014, 02:02:34 PM

Quote from: cryptonit on November 11, 2014, 01:06:01 PM

Quote from: Mister1k on November 11, 2014, 12:46:14 PM

This was a localized attack.IMHO

my main minting wallet was on the fork too i didnt mine at that pool
it was not local only connected to us.miningfield

west US backbone node and my minting wallet where affected too
when i was in fork i had never above 5 connections

so it was most likely just a handful wallets affected

ur between the line guess about attack origin i strong disbelieve there would be required skills to try such thing

reorg can work backwards far more than one block as i said before i tested once with over 600 blocks which did reorg back to mainchain

That is what i mean a local attack on Us. Miningfield. And he had to intervene correct? Yes!
So reorganize didn't work.Did he have to redownload the correct block chain? I believe so,but he could answer that.
And I'll spell it out for you,quote: ur between the line quess origin i strong disbelieve there would require skills to try such a thing. Well I strongly believe you pissed off one Utah John who has the skills.who was implementing a Us pool, that got the axe. A new replacement us .minigfield was implemented. Funny this was pool that was attacked. In less than week. If your minting wallet was affected and you weren't mining that pool You have got some serious issues. My miners were forked my wallet was not. I was minting aswell. Absolutely flawless. No problems with the wallet. So I ask you how was your wallet attacked because it was? The chain was forked for at least 6 hours and that is how many self healing blocks? Yah
There is a saying in this country. The toe you step on today might be the ass you kiss tomorrow..

Hi,

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.

s. http://www.miningfield.com
t. https://www.twitter.com/miningfield
f. https://www.facebook.com/miningfield
DMD Pool. http://eu.miningfield.com
http://us.miningfield.com