xencoin-seeder - Repo updated - initial seed changed for now - version data changed - https://github.com/thecarnie/xencoin-seeder
The XNC repo has my temporary xenseed node coded in - it should start downloading a blockchain right away without help from nodes in the xencoin.conf file... Be sure to remove them and delete your peers.dat file to test if it is connecting and finding nodes as expected. Still monitoring for a 10k orphan block exception during re-download. The chain is probably about 1/2 orphans mixed in from the bad diff algo and multi-pools. Will know more in the morning --
Building now. I'll add the coin to www.hasher.ca again for people to test with.
Finished, deleted blk* peers database etc... however, not connecting up:
2014-07-21 12:32:39 send version message: version 70002, blocks=0, us=192.99.35.133:1542, them=98.93.92.131:4334, peer=98.93.92.131:4334
2014-07-21 12:32:39 socket recv error 104
2014-07-21 12:32:39 disconnecting node 98.93.92.131:4334
2014-07-21 12:32:42 trying connection 98.93.92.131:4334 lastseen=73.3hrs
2014-07-21 12:32:42 connected 98.93.92.131:4334
2014-07-21 12:32:42 send version message: version 70002, blocks=0, us=192.99.35.133:1542, them=98.93.92.131:4334, peer=98.93.92.131:4334
2014-07-21 12:32:42 socket closed
2014-07-21 12:32:42 disconnecting node 98.93.92.131:4334
2014-07-21 12:32:44 trying connection 98.93.92.131:4334 lastseen=73.3hrs
$ xencoind getinfo
{
"version" : 80703,
"protocolversion" : 70002,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 0,
"timeoffset" : 0,
"connections" : 0,
"proxy" : "",
"difficulty" : 0.00024414,
"testnet" : false,
"keypoololdest" : 1405451347,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"errors" : ""
}
THANKS! That test alone shows several changes have worked. That IP you're seeing is my DDNS to my node working via the xenseed daemon running on my DL140 over here. Basically, the source last night has xenseed updated to host our own primary seeder, and I DDNSed my dev servers for now to keep the seeder going because I don't have any linux VMs facing the public at the moment.
The multiple connects to that IP basically show that I'm not down re-downloading the blockchain yet, so I'm not sharing blocks it seems.
I'm currently at about 675k since restarting last night. The checkpoints seem to have resolved the orphan mapping exhaustion issue I had yesterday, so progress. You might just shut the daemon down for a little bit on that one -- I'll ping a message up when I have the whole chain down and we can re-test to see if you start syncing up -
Thanks again man!
Ok great. What block should we actually be on, for the correct chain?
I started up my windows wallet and it sync'd up to 830k+