Sounds a lot like what was happening to me the other night. Re-downloading the blockchain multiple times with what were suppose to be the "trusted nodes" and then ending up on the wrong chain. With the assumption by others that I was somehow doing it wrong.

The next day I was finally able to download the correct chain with connect= (some node that was at one time posted in OP). The night before that node seemed to be down.

What I found really odd was that half of the blocks I had expected to be lost since I was on the wrong chain were confirmed in my wallet. Don't have the technical expertise here to explain that; but, it almost seemed as if I had mined blocks on both chains (doubt that is possible yet I can't explain it).

The problem with the "trusted" nodes is they themselves were moved to the wrong chain. I have removed them from the OP for now until they get on the right chain.

Thanks to a wonderful bit of knowledge from Sunny King I believe I have nailed down the issue

Once I am confident I have made the changes I will release a statement with the cause/ fix and all info pertaining to it.

For now Pertfiied has put up a list of nodes on the current chain. Redownloading the chain with those as addnodes should get you on the right chain ( which is the longer of the two ). If not connect= any of those nodes should get you directly connected to it and download the chain from them.

I will be working furiously to get the update pushed out tonight. Hopefully we can leave all these issues behind us

If your blockcount is matching the one below you are on the right chain

http://bottlecaps.kicks-ass.net/block_crawler.php

+1 i can't sync my wallet correctly with the OP's nodes.

Here is what is happening to my wallet... This is the reason many of us can not connect...

That long list of connections (I assume all linux compiles)...
Are all feeding this to us... (windows compiles v1.4.0)
{
"addr" : "199.192.205.46",
"services" : "00000000",
"lastsend" : 0,
"lastrecv" : 0,
"conntime" : 1376446605,
"version" : 0,
"subver" : "",
"inbound" : false,
"releasetime" : 0,
"startingheight" : -1,
"banscore" : 0
}


That is one of the connections, and they are all doing that, all IP's listed below, without xxxx's... from the list on the block-explorer... It connects for a split second, which is how I captured that info, then instantly disconnects us.

Notice VERSION: 0 and STARTINGHEIGHT: -1 and SERVICES: 0 and SUBVER: "", all null I assume, except the block, which may be null -1.

All connections are killing us, or we are killing all these connections...

We can't download the chain, because there are -1 blocks to download. (They are not speaking to us. Us windows users, I assume. WG, the windows compile is screwed-up. We connect fine when we are all on the same chain, win/linux... But now the correct chain seems to be only on linux, and it is not speaking to windows wallets. Check your "terminators"... windows is CRLF not just CR or LF, like linux or mac. Or the linux compiles are all botched, and not accepting windows data.)

These are the only ones speaking to us... (Even when we add the big list from the block-chains.)
[
{
"addr" : "70.98.114.237:7685",
"services" : "00000001",
"lastsend" : 1376447163,
"lastrecv" : 1376447164,
"conntime" : 1376447105,
"version" : 60008,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 72115,
"banscore" : 0
},
{
"addr" : "192.241.222.16:7685",
"services" : "00000001",
"lastsend" : 1376447118,
"lastrecv" : 1376447121,
"conntime" : 1376447117,
"version" : 60008,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 72115,
"banscore" : 0
},
{
"addr" : "199.180.115.100:7685",
"services" : "00000001",
"lastsend" : 1376447132,
"lastrecv" : 1376447133,
"conntime" : 1376447130,
"version" : 60008,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 72115,
"banscore" : 0
},
{
"addr" : "70.79.24.157:7685",
"services" : "00000001",
"lastsend" : 1376447348,
"lastrecv" : 1376447378,
"conntime" : 1376447343,
"version" : 60008,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 72116,
"banscore" : 0
}
]

Get one of those with the correct height, and we will all be in sync again...

NOTE: I have removed them from my list, and deleted peers, and the block-chain files... they always keep reconnecting to these four IP's...

Below is the long list (I have it setup to 100 connections, but the wallets only allow 8.) None connect, except the ones I xxxxxx'ed out... Which all have a block-height of 72115 now.

splash=0
server=1
gen=0
testnet=0
daemon=1
maxconnections=100
listen=1
xxxxxxxxxxxxxxxreservebalance=1000000

addnode=2.81.165.221
addnode=5.167.120.71
addnode=24.177.66.222
addnode=46.4.74.197
addnode=50.137.233.14
addnode=54.232.197.215
addnode=60.242.225.227
addnode=69.85.86.195
addnode=70.69.238.84
xxxxxxxxxxxxxxxxxxxxxxxaddnode=70.79.24.157
addnode=70.98.114.229
xxxxxxxxxxxxxxxxxxxxxxxaddnode=70.98.114.237
addnode=72.190.53.101
addnode=80.198.94.98
addnode=82.46.148.115
addnode=82.196.15.206
addnode=88.195.204.114
addnode=91.78.85.221
addnode=92.5.104.42
addnode=92.24.172.199
addnode=95.25.114.165
addnode=105.236.213.165
addnode=106.186.30.13
addnode=106.186.115.58
addnode=106.187.100.78
addnode=108.16.165.144
addnode=114.198.5.175
addnode=172.250.241.106
addnode=174.52.220.23
addnode=176.34.210.88
addnode=183.235.214.148
addnode=186.95.162.209
addnode=188.165.194.201
addnode=188.165.211.65
addnode=190.19.238.43
addnode=192.241.148.204
addnode=192.241.216.151
xxxxxxxxxxxxxxxxxxxxxxxxaddnode=192.241.222.16
addnode=192.241.222.102
addnode=199.192.205.46
xxxxxxxxxxxxxxxxxxxxxxxxaddnode=199.180.115.100
addnode=199.180.115.125
addnode=208.54.70.131
addnode=213.141.109.154

"startingheight" : 73204

Seems like the right height...

I assume you are not using the windows compiled wallet v1.4.0...

PM me, and I will send the log-file of a fresh connection to that list... From my windows client. It shows every connection connecting, then terminating, over and over, entering and exiting rooms, looking for connections which are in that list, and others. All with the same results.

What version of windows? (Mine is Win-7 home 64-bit.)

Also, are you using the v1.4.0 version? If yes, do you remember which link? (One of the links might have screwed-up compile settings. Like optimization and removal of error-checking or out-of-bounds checking.)

Same one as I have... but those connections are not working, the wallet is just going hyper disconnecting and joining tons of rooms, looking for more connections.

This is getting more strange with each day that passes. lol.

I am going to redownload both exe's and compare them. Though I doubt we are all corrupted, as others are still getting stuck on those four connections.

UPDATE: No luck... both still have the same results.

The only other thing I can think-of, is "home" does not offer language-packs, other than default. Is it possible someone in the chat-rooms is broadcasting ISO:Chrs that home users can't "translate", without having the language-packs. (If it is not a "terminator" issue, it may be a ISO:chr format issue.)

Win-home only has a few languages. Windows fails to convert other ISO standards, unless you get the ultimate or pro versions. (Similar things happen on japanese and chinese websites and programs.)

EDIT: I can think of one more issue... could my IP be rejected, from being listed with a banscore? IP's are not fixed, and mine rolls every few days. How do you check something like that? (If they are rejecting my connection, because of a banscore... I have no clue who had this IP before me. IP banning is as useless as cookie-banning. lol. It would be odd that I was IP-banned from every single correct chain, and IP, except the four with the wrong-height, which is the four I was mining on for weeks, without issue, and still connect to.)

The 1.41 should be out very soon we are testing it right now to assure its working as planned. Sunny King assisted with the fix to PoS to ensure we have no issues in the future. This update will be required and block out the older clients causing issues.

We will release a detailed explanation of everything when the wallet release takes place. Thanks again for being patient ans supporting the coin!

check your debug log files and you can see what irc you connecting to and then check them to see if they have banned or put a temp hold on your ip.