Quote from: patapato on April 08, 2015, 01:40:08 PM

To worsen things, a trusted forger thought that he was on a bad fork, so he tried to reset his blockchain, stopping forging on his original blockchain and getting in sync with the attacker's fork:

Quote from: User1397367406 on April 07, 2015, 11:18:51 PM

I tried syncing a client on my computer from mid march and so far it seems to sync until block 277934 and 277940 :
...

I tried to sync a client on my main computer, different from my forging node, and ended up with the above mentioned result. I wanted to see what would happen.
I re-started my forging node yesterday and stopped forging on it, it's still there doing nothing, at block 280284 4/7/2015 22:19:56, connected to 4 nodes: funkyvps3, patapato, 99.227.*.* and 106.187.*.*
The blockchain was not reset but i was forging all the block and so maybe i'm on my own fork.

Quote from: patapato on April 08, 2015, 01:40:08 PM

Solutions?:

I ask you, @User1397367406, to please recover your last original blockchain, as you forged in sync with me at least until height 279189 (06/04/2015 21:10:52, GMT+2), while you are currenly going back to 277934.
I ask every forger to blacklist lcharles node: nxt.servebeer.com (46.105.44.4)
I will distribute my account balance in smaller accounts, roughly the size of the next big forger, in order to have a more equilibrated distribution of forging power

Other suggestions, comments, ideas?

I'll blacklist lcharles node. Not sure if i ever saw his node connected. Should start taking screenshots of the connected nodes and such Wink

I'll try connecting my other client to see what happen, enabling some logging.

I agree on only distributing/leasing a smaller amount of NAS.