I don't know who it is, but atleast it's easy to mine then .

I use to mine XenCoin earlier. It was a lucrative way to earn some other coins, like trading them for LTC or BTC.

I still own a few. I really hope they will be worth more in the future.

The xnc.Altcoins.pw pool is being converted to out new domain along with all our other pools!!!

12:42:57

[
{
"addr" : "216.56.62.132:4588",
"services" : "00000001",
"lastsend" : 1396539752,
"lastrecv" : 1396539773,
"conntime" : 1396534781,
"version" : 60080,
"subver" : "/Satoshi:1.1.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 86046,
"banscore" : 0
},
{
"addr" : "176.31.128.78:28770",
"services" : "00000001",
"lastsend" : 1396539761,
"lastrecv" : 1396539728,
"conntime" : 1396535030,
"version" : 60001,
"subver" : "/42:0.6.4.6/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 46162,
"banscore" : 0
},
{
"addr" : "62.254.202.137:7536",
"services" : "00000003",
"lastsend" : 1396539705,
"lastrecv" : 1396539769,
"conntime" : 1396535912,
"version" : 60003,
"subver" : "/Satoshi:0.8.5/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 35907,
"banscore" : 0
},
{
"addr" : "12.35.115.132:24242",
"services" : "00000001",
"lastsend" : 1396539773,
"lastrecv" : 1396539737,
"conntime" : 1396537026,
"version" : 60001,
"subver" : "/42:0.6.4.6/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 46175,
"banscore" : 0
},
{
"addr" : "185.14.233.3:12127",
"services" : "00000001",
"lastsend" : 1396539770,
"lastrecv" : 1396539755,
"conntime" : 1396538256,
"version" : 60001,
"subver" : "/Satoshi:0.6.3/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1162872,
"banscore" : 0
},
{
"addr" : "24.113.141.54:24242",
"services" : "00000001",
"lastsend" : 1396539773,
"lastrecv" : 1396539745,
"conntime" : 1396539456,
"version" : 60001,
"subver" : "/42:0.6.4.6/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 46205,
"banscore" : 0
},
{
"addr" : "81.207.225.166:9336",
"services" : "00000001",
"lastsend" : 1396539774,
"lastrecv" : 1396539764,
"conntime" : 1396539613,
"version" : 60002,
"subver" : "/Satoshi:0.6.4.4/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 192977,
"banscore" : 0
}
]


these are what I have... that don't seem to do anything...

Any news?

Here's my current list again:

[
    {
        "addr" : "192.99.44.51:9556",
        "services" : "00000001",
        "lastsend" : 1397310524,
        "lastrecv" : 1397310499,
        "conntime" : 1396286428,
        "version" : 60001,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 49264,
        "banscore" : 0
    },
    {
        "addr" : "209.99.52.73:9333",
        "services" : "00000001",
        "lastsend" : 1397310541,
        "lastrecv" : 1397310528,
        "conntime" : 1396296828,
        "version" : 60001,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 541299,
        "banscore" : 0
    },
    {
        "addr" : "[2604:180:1::497:4efc]:4334",
        "services" : "00000001",
        "lastsend" : 1397310542,
        "lastrecv" : 1397310548,
        "conntime" : 1396812998,
        "version" : 60001,
        "subver" : "/Satoshi:0.6.3.3/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 678648,
        "banscore" : 0
    },
    {
        "addr" : "24.216.160.116:9333",
        "services" : "00000001",
        "lastsend" : 1397310543,
        "lastrecv" : 1397310539,
        "conntime" : 1397168907,
        "version" : 60001,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 547222,
        "banscore" : 0
    },
    {
        "addr" : "173.68.64.253:9333",
        "services" : "00000001",
        "lastsend" : 1397310542,
        "lastrecv" : 1397310547,
        "conntime" : 1397191310,
        "version" : 60001,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 547386,
        "banscore" : 0
    },
    {
        "addr" : "89.105.153.50:9333",
        "services" : "00000001",
        "lastsend" : 1397310546,
        "lastrecv" : 1397310546,
        "conntime" : 1397221214,
        "version" : 60001,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 547552,
        "banscore" : 0
    },
    {
        "addr" : "73.54.176.143:9333",
        "services" : "00000001",
        "lastsend" : 1397310536,
        "lastrecv" : 1397310536,
        "conntime" : 1397229682,
        "version" : 60001,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 547610,
        "banscore" : 0
    },
    {
        "addr" : "109.150.134.0:9333",
        "services" : "00000001",
        "lastsend" : 1397310529,
        "lastrecv" : 1397310546,
        "conntime" : 1397297069,
        "version" : 60001,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 548052,
        "banscore" : 0
    }
]

Thanks Crackfoo - that's got it sorted 

The problem right now is the client uses insecure OpenSSL and is vulnerable.

The dev promised updates, and has done absolutely nothing.  Now, he's got an insecure client on his hands...

I'm going to go ahead and compile clients with the new OpenSSL and post them on my Github Repo.  I'll also add a few checkpoints for the blockchain.

If anyone has reliable dedicated seednodes, I'll add those as well.

Other than that -- I can't put much time into this coin at all.  The dev makes false promises so he can dump more of his coins.  ScryptASICs are here (and more are coming) -- it could grow into something nice, although right now the chain and the client are not secure.  Chain because of lack of hashing power - client because of OpenSSL.

In all reality, the chain needs to be forked, with some fixes for difficulty adjustment and the block times need to be changed a little.  20 seconds is too fast to be stable and secure, IMO.  It needs to be at least 2 minutes per block...

Personally, I've come on some tight financial times, or I would be provisioning a couple seed servers and a new website so that the members could initiate a community takeover of the coin.  I feel we've all given the dev enough time to make things right for us all, and he/she/whoever has only blown smoke up our asses...

For a DNS Seed node, there's a seperate daemon that is a crawler/DNS Server (modified) -- it can run on the same machine as you would run a pool on I would think but there might be some port trickery to make it all jive.  In the client, we would record the seed node's DNS name -- I have a few domains I could put records on and point to whatever IPs we use - then for the DNS seed-daemon - it basically crawls the network looking for valid nodes of any type (can be version limited), and keeps track of them - then when the clients do a startup looking for peers, it requests some nodes from the seed-node and so on.  The seeder keeps track of good and bad nodes and bans bad ones and so forth.  It essentially eliminates the need for nodes in the xencoin.conf file once you have a couple good stable seed nodes up there --

Technically any alt-coin that is weak in hashing/nodes needs a couple DNS seeders out there just so that clients can be fired up and start taking to other clients to grab the blockchain.  The DNS seed nodes themselves don't necessarily share the blockchain.  A 'regular' seed node would be just a client that is up and running with the chain available for download - so it needs a decent connection on the outbound side to be reliable and quick - otherwise, it doesn't mine or anything - just shares the blockchain and helps coordinate the 'available node' pool --

DNS Seeds help the 'clients' find other 'clients' so they can sync and download the blockchain --

The only one I found so far was designed for Bitcoin -- so I was going to pull the code and see if it needed modifying as far as 'default ports' and such to make it proper -- the other problem we have is the client was originally cloned from another coin and the dev didn't bother to change a couple things in the code, so that's part of why we get the loss of sync sometimes and it trying to pickup the wrong chain..  I'm not sure there's much that can be done about that -- but otherwise , I think there's a little of a plan at least to recover where this person just fell off now that the coin has albeit tanked in value --

I'll update most likely in the morning when I've had a little time to look at the source