Quote from: digeros on August 15, 2013, 12:10:35 AM

Quote from: Palmdetroit on August 15, 2013, 12:01:37 AM

Quote from: digeros on August 14, 2013, 11:46:43 PM

Quote from: Palmdetroit on August 14, 2013, 10:55:29 PM

Quote from: Moray on August 14, 2013, 10:51:25 PM

Yep, 42 connections on the first, and 11 on the second wallet. Thank you!.

yes good drown out all those bad nodes Grin

When I look at getpeerinfo IS there any way to determine if one of those nodes is propagating a bad blockchain???

for example should I compare the last block rec'd and get rid of the ones that are far behind???

"addr" : "76.XXX.XXX.XXX:50505",
"services" : "00000001",
"lastsend" : 1376523374,
"lastrecv" : 1376523713,
"conntime" : 1376523298,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 12045,
"banscore" : 0

digeros

When I type it in a I see about 20-30% giving bad info typically they are kinda grouped on the same blocks

9346 is def people running the bugged 1.2 the well known 6084, etc

in field "startingheight"

there is so many on wrong chains... that is the big problem... not sure why,

SO, it is the STARTING HEIGHT THAT SHOULD MATCH ACROSS THE NETWORK???

I am running V1.2 Beta and MOST of my nodes last rec'd are all within about 10-20 blocks of each other so I guess that all of them are really OK. digeros

ya nodes are downloading blocks as time goes on too, some of the dead ends are mining on those broke chain too , I think anyway. They tend to live in clusters Cheesy

Its actually improved much since 1.2beta1