We're up to just under 900k blocks (I'm showing two nodes with 899k (mine which is still pulling) and triptech's.  I'm currently at 700k blocks so I think within the next hour or so it will be servicing other nodes

Is that with the new code or your original wallet?

You might try this:  

The clients (most) have two 'ways' to connect - one is addnode=, the other is connect= .  The windows client "might" benefit from using connect= in your xencoin.conf and triptech's IP for now -- that tells the client to connect directly to another node and ignore peers and seeds -- maybe it will help you get up to speed on connections - once the chain is down, you should be able to remove it and restart - I would think it would stay synced then.  The issue is the lack of checkpoints in the chain on the old clients -- so they continually get stuck...

EDIT:  My xenseed only shows two other clients besides mine running on port 4334 (default) for XNC - there should be a few more with the exchanges but they are not showing up - and I'm willing to bet that the three are you, me, and tt.

That was just the orig windows QT.

My linux binary, just crashed:

xencoind:usr/include/boost/thread/pthread/recursive_mutex.hpp:92: boost::recursive_mutex::~recursive_mutex(): Assertion `!pthread_mutex_destroy(&m)' failed.

If you have a wallet going that is coin-safe, I wouldn't see the problem to be honest.  4334 is the 'protocol' port, and 4335 is the RPC port (for server and mining) -- so if you open 4334 we will see the node popup and help share the chain

Noticed in my testing that on my linux build, during the blockchain download, there were some issues and it 'corrupted' the wallet somehow.  After I pulled down the entire chain, I ran a -salvagewallet on that box and it came up no problem and has stayed alive for 24+ hours now --

Still working out the QT build but making progress -- the daemon builds seem to be working for linux and windows - but we're still testing --

Status: 0/unconfirmed, broadcast through 7 nodes
Date: 7/22/2014 13:34
To: XyuH7qjfAw4Q9n3Hc9iSonkKKpoAkibxDj
Debit: -10.00 XNC
Net amount: -10.00 XNC
Transaction ID: e4b43cd2e870da5b4a13eb6a934b36b0aaf7dc1c04d71ffbb1fcaae9073d95db

From my old wallet.

{
"version" : 60303,
"protocolversion" : 60001,
"walletversion" : 60000,
"blocks" : 903551,
"connections" : 8,
"proxy" : "",
"difficulty" : 0.01117148,
"testnet" : false,
"keypoololdest" : 1392226968,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00010000,
"errors" : ""
}

I've got a ticket open with Cryptsy at the moment and got this e-mail yesterday 'Our technical team has placed the XNC wallet under maintenance.  I will update you soon as it is back online. Sorry for the inconvenience and thank you for your patience.'

Hopefully their on it - I've got several transactions that haven't made it through to them!

I opened my ticket on the 6th July......

Not sure any of them look very promising...


"addr" : "46.32.253.168:4334",
"services" : "00000001",
"lastsend" : 1406055012,
"lastrecv" : 1406055012,
"conntime" : 1405961460,
"version" : 60001,
"subver" : "/XencoinTT:0.6.4.8/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 899383,
"banscore" : 0
},
{
"addr" : "5.129.241.223:9333",
"services" : "00000001",
"lastsend" : 1406055013,
"lastrecv" : 1406055008,
"conntime" : 1405972759,
"version" : 60001,
"subver" : "/Satoshi:0.6.3/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 608335,
"banscore" : 0
},
{
"addr" : "68.45.217.68:9333",
"services" : "00000001",
"lastsend" : 1406055013,
"lastrecv" : 1406055013,
"conntime" : 1405995358,
"version" : 60001,
"subver" : "/Satoshi:0.6.3/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 608485,
"banscore" : 0
},
{
"addr" : "77.100.113.204:11081",
"services" : "00000001",
"lastsend" : 1406054907,
"lastrecv" : 1406052547,
"conntime" : 1406015056,
"version" : 70001,
"subver" : "/WorldcoinFoundation:0.8.5.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1293352,
"banscore" : 0
},
{
"addr" : "151.62.79.149:11081",
"services" : "00000001",
"lastsend" : 1406054895,
"lastrecv" : 1406054906,
"conntime" : 1406026817,
"version" : 70001,
"subver" : "/WorldcoinFoundation:0.8.5.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1293352,
"banscore" : 0
},
{
"addr" : "71.62.122.227:9333",
"services" : "00000001",
"lastsend" : 1406055013,
"lastrecv" : 1406055013,
"conntime" : 1406035817,
"version" : 70002,
"subver" : "/Satoshi:0.8.5.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 608735,
"banscore" : 0
},
{
"addr" : "86.163.167.12:4334",
"services" : "00000001",
"lastsend" : 1406055013,
"lastrecv" : 1406055013,
"conntime" : 1406040811,
"version" : 60001,
"subver" : "/Satoshi:0.6.3.3/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 903231,
"banscore" : 0
},
{
"addr" : "98.93.94.158:4334",
"services" : "00000003",
"lastsend" : 1406055013,
"lastrecv" : 1406054998,
"conntime" : 1406054624,
"version" : 70002,
"subver" : "/Xencoin:0.8.7.3/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 903959,
"banscore" : 0
}

Depending on when you talk to them next, you can let them know of the xenseed.liquidbbs.org as an addnode so they can start finding peers.  They'll need to update their wallet soon when post the 'release' tag on the source because the next round of updates after this one will start rejecting old wallets after we've run these new ones for a little while.  This way we can stop getting the pollution from the old clients as well as start moving forward on our proposed updates to the coin for the long-term...