Re: NAS :: Descendant of NXT 100% PoS|More Exchanges|WinNAS is ready!
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.
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.
Thank you User1397367406, I'm glad that you didn't reset your main forging node. I agree that better you stop forging until other forger reach you. I was on that situation before, forging alone ahead of the rest, and my node resynchronized by itself when others reached my block height:
Hey!, I am synchronized again 
I didn't stop my node, just I stopped to forge and it synchronized after 5.5 hours, here is the block history of that time (GMT+1):
...
260632 18/03/2015 23:00:54 0 0 0 NAS-5HZF-TPQ5-GSHF-7GV33 0 B 8708 %
260631 18/03/2015 22:59:17 0 0 0 NAS-5HZF-TPQ5-GSHF-7GV33 0 B 5386 %
260630 18/03/2015 16:29:59 0 0 0 NAS-H5AW-7J9F-7VCY-DJ8NB 0 B 2693 %
260629 18/03/2015 16:28:10 0 0 0 NAS-H5AW-7J9F-7VCY-DJ8NB 0 B 1482 %
...
I didn't stop my node, just I stopped to forge and it synchronized after 5.5 hours, here is the block history of that time (GMT+1):
...
260632 18/03/2015 23:00:54 0 0 0 NAS-5HZF-TPQ5-GSHF-7GV33 0 B 8708 %
260631 18/03/2015 22:59:17 0 0 0 NAS-5HZF-TPQ5-GSHF-7GV33 0 B 5386 %
260630 18/03/2015 16:29:59 0 0 0 NAS-H5AW-7J9F-7VCY-DJ8NB 0 B 2693 %
260629 18/03/2015 16:28:10 0 0 0 NAS-H5AW-7J9F-7VCY-DJ8NB 0 B 1482 %
...