Quote from: patapato on April 07, 2015, 12:17:48 PM

I created a new account, and I sent it 1000 NAS (transaction 18419636354574564653). I was not forging in that instant. But I didn't get blocks, so I started forging again. In my blockchain it is at height 279190 forged by me, but in tiker's public node (http://funkyvps3.funkymonkey.org:7873/) it is at height 277935 forged by NAS-VBK9-5ZXA-CJQ8-GEWVU (with a balance of 64 NAS).

I am observing in real time how both forks are fighting, as I see the block height going back and forth in both nodes. Interesting.

My nodes are stuck at 277935. They are sticking with block 277934 and attempting to link 277935 to it. At first when my node was forging, it was trying to stick it's own forged block there but other nodes didn't agree. A block forged by NAS-3S5R-Q4ZL-QUEA-BWAP2 was there for a short time but it removed it because other nodes didn't agree. My nodes keep destroying all blocks from 277935 and onwards and trying to rebuild them. That is why you now see your transaction in that block but it'll be destroyed soon as it attempts to rebuild it again.

My nodes appear to be rejecting the block 277935 that other nodes are trying to pass to it. It gives a bad signature message and bans that IP for 15 minutes or so. That would make me think that my block 277934 is different than the same block number everyone else has.

I had shut down my local NAS client over night and just started it up again. I'll see what it does.

I just hope bter's node isn't suck like mine. It won't be good if it is.