Quote from: tiker on April 07, 2015, 04:33:13 PM

I think the bter.com node is stuck with my nodes.

The peer list from my public node:

Code:

Address Weight Downloaded Uploaded Application Platform
cb2.flipflop.mooo.com 0 47 MB 71 KB NRS 1.1.3.N1 CubieBoard2
99.227.137.145 0 1 MB 1 MB NRS 1.1.3.N1 PC
patapato.ddns.net 0 64 MB 205 KB NRS 1.1.3.N1 Win7-64b
106.187.102.227 0 4 MB 4 MB NRS 1.1.3.N1 PC
cb2.flipflop.mooo.com 1'972'503 80 MB 125 KB NRS 1.1.3.N1 CubieBoard2

If you look at the downloaded MB counts, 3 nodes which agree are all 50+ MB and are constantly trying to update my public node with their block chains.

My local node (99.227....) and bter's node (106.187...) are both under 10 MB which makes me think they're in agreement with my public node's chain and are trying to continue from there. We need to find a way to get the nodes to resolve the issue on their own. I won't be good for us if we ask bter to reset their node...

I'll start forging on both nodes again. The account on my public node will be forging with about 8 NAS and my local node will be forging with a little over 5000 NAS.

Another thing to point out... The consoles for both nodes are reporting signature errors for the blocks. I've also noticed that the hallmarked nodes are not showing as hallmarked nodes all the time. (Weight = 0 in the list above.) I have seen evidence of a signature generation problem from my public node when I attempted to send out a transaction in the past. There might be more to this problem than just a forked chain.

How do you know bter's node is (106.187...)?