Pages:
Author

Topic: [ANN][XNC] XenCoin | Instant | Stable | Long term Support - New UPDATE!!! - page 5. (Read 75744 times)

legendary
Activity: 1470
Merit: 1010
Join The Blockchain Revolution In Logistics
XenCoin.com is for sale (Xen Coin)

Click here to buy XenCoin.com for $2,395

hash rate = 5mh

 Cry
legendary
Activity: 3570
Merit: 1126
Another perma node added:

46.32.253.168:4334 - my wallet build  (perm node the daddy node lol)
212.48.71.178:9333 - Carnies wallet build (new perm node)
86.163.167.12:4334 - my wallet build (semi-perm node)


You should be able to see my perm node at 192.99.35.133
newbie
Activity: 17
Merit: 0
I've setup a permanent seed node -- it's doing some testing at the moment and I'm finalizing some changes to the seeder code.  When both are up, I'll post the DNS names, and make updates to the repos I have.  The updates will help any NEW builds AUTOMATICALLY find peers and hosts without need for a xencoin.conf file to add nodes and connections.  The first phase of stabilizing the network as far as connectivity is almost complete. 

Next will be beta testing of the client updates for a release.


Good work that man!
full member
Activity: 136
Merit: 100
I've setup a permanent seed node -- it's doing some testing at the moment and I'm finalizing some changes to the seeder code.  When both are up, I'll post the DNS names, and make updates to the repos I have.  The updates will help any NEW builds AUTOMATICALLY find peers and hosts without need for a xencoin.conf file to add nodes and connections.  The first phase of stabilizing the network as far as connectivity is almost complete. 

Next will be beta testing of the client updates for a release.
newbie
Activity: 17
Merit: 0
Another perma node added:

46.32.253.168:4334 - my wallet build  (perm node the daddy node lol)
212.48.71.178:9333 - Carnies wallet build (new perm node)
86.163.167.12:4334 - my wallet build (semi-perm node)
full member
Activity: 136
Merit: 100
I'm working on daemon-izing the xenseeder -- it's about ready -- Once I get that posted to github, we can bring the seed nodes online and I'll add their dns names/IPs into the code -- then, we'll add those nodes into the source for the update.  This will allow more updated copies out for testing that are ready - currently, the seednode data is insufficient to set for testing Smiley
legendary
Activity: 3570
Merit: 1126
thecarnie - I got a VPS farm ready to go online.

Do you think its worth using the existing wallet, my build with checkpoints up to approx 860k or yours?

Cheers boss.

I pulled your checkpoints into the source tree and that's what my current QT and linux wallet are running with.  I had a hiccup with the seeder that reset my peercache and so my  two wallets and most likely some others out there were having a hard time staying connected.  I'll know more with the other updates and once I clean out some more loose ends in the QT portion of the wallet.

I also am going to need to get some testers out there with the new QT wallet once I get a beta online.  So far, compiled with QT-5.2.1 and Boost 1.55 (mingw64-4.8-GCC) it is stable but I'm noticing some network quirks that might be related to an LTC issue they were having as well.  More on that when I pinpoint the issue Smiley


I'll test it out when you have something ready.
full member
Activity: 136
Merit: 100
thecarnie - I got a VPS farm ready to go online.

Do you think its worth using the existing wallet, my build with checkpoints up to approx 860k or yours?

Cheers boss.

I pulled your checkpoints into the source tree and that's what my current QT and linux wallet are running with.  I had a hiccup with the seeder that reset my peercache and so my  two wallets and most likely some others out there were having a hard time staying connected.  I'll know more with the other updates and once I clean out some more loose ends in the QT portion of the wallet.

I also am going to need to get some testers out there with the new QT wallet once I get a beta online.  So far, compiled with QT-5.2.1 and Boost 1.55 (mingw64-4.8-GCC) it is stable but I'm noticing some network quirks that might be related to an LTC issue they were having as well.  More on that when I pinpoint the issue Smiley
legendary
Activity: 3570
Merit: 1126
Wow, network hashrate ALOT higher!!

haha yeah, I'm sucking a few XNC out of it Wink Wink

2200 blocks in the past couple days
member
Activity: 95
Merit: 10
Wow, network hashrate ALOT higher!!
newbie
Activity: 17
Merit: 0
thecarnie - I got a VPS farm ready to go online.

Do you think its worth using the existing wallet, my build with checkpoints up to approx 860k or yours?

Cheers boss.
full member
Activity: 136
Merit: 100
darn, also looks like Cryptsy has the wallet offline.

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!

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...



I've had the seeder running, but not sure it's getting much:

[14-07-24 09:41:11] 0/8 available (1 tried in 323s, 0 new, 7 active), 0 banned; 0 DNS requests, 0 db queries


0/8  available?

What DNS name is this at so I can add it to my local source tree and test with it.  I had some form of network failure on my end and it took xenseed.liquidbbs.org offline and both my clients.  Now, both clients are all pissed off over stale peers...  My seeder is back up, but I'm still having other stability issues at the moment I'm tracking down...

full member
Activity: 136
Merit: 100
darn, also looks like Cryptsy has the wallet offline.

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!

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...



I've had the seeder running, but not sure it's getting much:

[14-07-24 09:41:11] 0/8 available (1 tried in 323s, 0 new, 7 active), 0 banned; 0 DNS requests, 0 db queries


0/8  available?

The seeder most likely is not answering DNS queries because I haven't included that DNS name in the source update just yet.  On the flip side, on that machine, is port 53 open in IPTABLES and available?   FWIW, here's the stats from xenseed.liquidbbs.org (restarted yesterday for code update):



The "active" count is only 'alive' hosts that it's tracking.  They don't necessarily reflect XNC hosts by any means.  When I pool the dnsseed.dump file for 4334 ports or 0.6.3.3 (the XNC version string for old clients) - it only comes up with about 6 total that match.  My QT waller is maintaining 17 connections right now, but only 8 of them trace back to XNC clients - the other 8 are the QT wallet connecting, verifying, then disconnecting from clients that are serving other coins.  Here's a 'getpeerinfo' from my client with 'invalid hosts' removed:

Code:
[
{
// BAD HOST REMOVED
},
{
// BAD HOST REMOVED
},
{
"addr" : "86.163.167.12:4334",
"services" : "00000001",
"lastsend" : 1406236344,
"lastrecv" : 1406236499,
"bytessent" : 126993,
"bytesrecv" : 863998,
"blocksrequested" : 0,
"conntime" : 1406188626,
"version" : 60001,
"subver" : "/Satoshi:0.6.3.3/",
"inbound" : false,
"startingheight" : 912872,
"banscore" : 0
},
{
//BAD HOST REMOVED
},
{
//BAD HOST REMOVED
},
{
//BAD HOST REMOVED
},
{
//BAD HOST REMOVED
},
{
"addr" : "72.46.152.250:36936",
"services" : "00000001",
"lastsend" : 1406236462,
"lastrecv" : 1406236350,
"bytessent" : 78793,
"bytesrecv" : 6492,
"blocksrequested" : 0,
"conntime" : 1406235421,
"version" : 60001,
"subver" : "/Satoshi:0.6.3.3/",
"inbound" : true,
"startingheight" : 913285,
"banscore" : 0
},
{
"addr" : "204.11.237.203:41605",
"services" : "00000001",
"lastsend" : 1406236505,
"lastrecv" : 1406236515,
"bytessent" : 78986,
"bytesrecv" : 5842,
"blocksrequested" : 2,
"conntime" : 1406235451,
"version" : 60001,
"subver" : "/Satoshi:0.6.3.3/",
"inbound" : true,
"startingheight" : 913285,
"banscore" : 0
},
{
"addr" : "5.43.136.57:58937",
"services" : "00000001",
"lastsend" : 1406236470,
"lastrecv" : 1406236519,
"bytessent" : 80667,
"bytesrecv" : 4844,
"blocksrequested" : 0,
"conntime" : 1406235462,
"version" : 60001,
"subver" : "/Satoshi:0.6.3.3/",
"inbound" : true,
"startingheight" : 913285,
"banscore" : 0
},
{
"addr" : "46.188.28.6:64518",
"services" : "00000001",
"lastsend" : 1406236451,
"lastrecv" : 1406236392,
"bytessent" : 78390,
"bytesrecv" : 2923,
"blocksrequested" : 0,
"conntime" : 1406235490,
"version" : 60001,
"subver" : "/Satoshi:0.6.3.3/",
"inbound" : true,
"startingheight" : 913285,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "122.233.43.13:30474",
"services" : "00000001",
"lastsend" : 1406236474,
"lastrecv" : 1406236520,
"bytessent" : 80826,
"bytesrecv" : 3843,
"blocksrequested" : 0,
"conntime" : 1406235511,
"version" : 60001,
"subver" : "/Satoshi:0.6.3.3/",
"inbound" : true,
"startingheight" : 913286,
"banscore" : 0
},
{
"addr" : "46.10.101.27:63774",
"services" : "00000001",
"lastsend" : 1406236518,
"lastrecv" : 1406236439,
"bytessent" : 77215,
"bytesrecv" : 2383,
"blocksrequested" : 0,
"conntime" : 1406235531,
"version" : 60001,
"subver" : "/Satoshi:0.6.3.3/",
"inbound" : true,
"startingheight" : 913287,
"banscore" : 0
},
{
"addr" : "79.172.16.8:51773",
"services" : "00000001",
"lastsend" : 1406236514,
"lastrecv" : 1406236508,
"bytessent" : 78494,
"bytesrecv" : 1728,
"blocksrequested" : 0,
"conntime" : 1406235549,
"version" : 60001,
"subver" : "/Satoshi:0.6.3.3/",
"inbound" : true,
"startingheight" : 913288,
"banscore" : 0
},
{
"addr" : "2.30.2.193:51165",
"services" : "00000001",
"lastsend" : 1406236455,
"lastrecv" : 1406236450,
"bytessent" : 76454,
"bytesrecv" : 3267,
"blocksrequested" : 0,
"conntime" : 1406235582,
"version" : 60001,
"subver" : "/Satoshi:0.6.3.3/",
"inbound" : true,
"startingheight" : 913289,
"banscore" : 0
},
{
"addr" : "2.30.2.193:63508",
"services" : "00000001",
"lastsend" : 1406236389,
"lastrecv" : 1406236341,
"bytessent" : 77276,
"bytesrecv" : 2110,
"blocksrequested" : 0,
"conntime" : 1406235592,
"version" : 60001,
"subver" : "/Satoshi:0.6.3.3/",
"inbound" : true,
"startingheight" : 913289,
"banscore" : 0
},
{
"addr" : "83.30.124.27:61746",
"services" : "00000001",
"lastsend" : 1406236515,
"lastrecv" : 1406236502,
"bytessent" : 78022,
"bytesrecv" : 2329,
"blocksrequested" : 1,
"conntime" : 1406235628,
"version" : 60001,
"subver" : "/Satoshi:0.6.3.3/",
"inbound" : true,
"startingheight" : 913289,
"banscore" : 0
},
{
"addr" : "68.117.4.111:47629",
"services" : "00000001",
"lastsend" : 1406236517,
"lastrecv" : 1406236454,
"bytessent" : 77245,
"bytesrecv" : 1447,
"blocksrequested" : 0,
"conntime" : 1406235700,
"version" : 60001,
"subver" : "/Satoshi:0.6.3.3/",
"inbound" : true,
"startingheight" : 913290,
"banscore" : 0
},
{
//BAD HOST REMOVED
},
{
"addr" : "24.4.45.219:52502",
"services" : "00000001",
"lastsend" : 1406236497,
"lastrecv" : 1406236510,
"bytessent" : 75496,
"bytesrecv" : 549,
"blocksrequested" : 0,
"conntime" : 1406236435,
"version" : 60001,
"subver" : "/Satoshi:0.6.3.3/",
"inbound" : true,
"startingheight" : 913293,
"banscore" : 0
},
{
"addr" : "198.177.58.54:52973",
"services" : "00000001",
"lastsend" : 1406236482,
"lastrecv" : 1406236480,
"bytessent" : 75441,
"bytesrecv" : 384,
"blocksrequested" : 0,
"conntime" : 1406236480,
"version" : 60001,
"subver" : "/Satoshi:0.6.3.3/",
"inbound" : true,
"startingheight" : 913293,
"banscore" : 0
}
]
full member
Activity: 136
Merit: 100


ARE YOU A MORON??? MAKE YOUR SHITS WITH ANOTHER COIN!!! AND YOU GO FUCK ITSELF!

Unless you've got something constructive to add I suggest you stop posting on this thread.

This isn't your coin anymore.  

 Grin  Grin  Grin Will see...

I got one better, fucko --

OFFICIAL ANNOUNCEMENT FOR XENCOIN MINERS:
[ UPDATE COMING ]
END ANNOUNCEMENT

So after a week of bailing out this chain, so the people that have carried it for over a year while YOU sit around and do nothing, and you respond with a go-fuck-yourself instead of a "Thanks for the update, I'll merge it into the master branch and release it" - well, you sir (or ma'am) are a fucktard.  You should watch REAL HARD who you fuck with.  Your network hashrate averages less than 5MH/s.  NEVER FORGET THAT THE MINERS ARE WHO CARRIES YOUR NETWORK.  If the miners and a developer agree on what they want, you're fucked.  Plain and simple.  We could just as easily write changes to the client that invalidate the first 100000 or more blocks of the chain, making ANY coins you hold worthless.  Since you haven't done a FUCKING THING to save your coin, including letting both your domains expire, and never updating a single thing in your source tree since release, don't be surprised when your network abandons you and leave you sitting.  The major exchanges are already debating on pulling your client.  Without an exchange - you're really fucked.  

So -- that being said -- I think, rather, that you can go fuck yourself and take your coin with you.  I got a biscuit for ya -- nice, brown, and fresh...  Hungry?
legendary
Activity: 3570
Merit: 1126
darn, also looks like Cryptsy has the wallet offline.

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!

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...



I've had the seeder running, but not sure it's getting much:

[14-07-24 09:41:11] 0/8 available (1 tried in 323s, 0 new, 7 active), 0 banned; 0 DNS requests, 0 db queries


0/8  available?
legendary
Activity: 3570
Merit: 1126

Are there any XenCoin accepting sites at this moment? Is there an overview somewhere?
Except for the exchanges, obviously :-)

@thecarnie: Keep up the good work. Nice to see there is active development on this coin!

The only summary information available at this moment is on the first page of this topic.  The coin was pump and dumped by the original dev, and it has a huge premine sitting around that we haven't been able to trace just yet. 

I'm fighting the QT libraries at the moment to get a new set of clients built and released for now - while I finish bringing the rest of the updates and fixes into the client from the other coins -- Once we get the client re-released with new SSL and checkpoints, we're going to try to offer some bounties to get some more places to accept it for use.  I'm also working out a couple other ideas in the back of my head for usage as well -- if you have any ideas, feel free to add to this topic until we get the new one and forums online on it's own site Smiley



MAKE YOUR SHITS WITH ANOTHER COIN!!!

Well you just freed up a bunch of my time.  Fuck you too.  You can say what ever you want.  Your actions and your treatment of this coin, and it's supporters with that post I guarantee just got you a coin worth jack shit.  I hope it drops to 0 now and gets dumped from the exchanges.

Peace out guys...  I'm done here.  I've vested too much time for a response like that.


ARE YOU A MORON??? MAKE YOUR SHITS WITH ANOTHER COIN!!! AND YOU GO FUCK ITSELF!

Seriously, this is your response again? This is the type of developer that need to be flushed out of this coin. And you will.
member
Activity: 77
Merit: 10

Are there any XenCoin accepting sites at this moment? Is there an overview somewhere?
Except for the exchanges, obviously :-)

@thecarnie: Keep up the good work. Nice to see there is active development on this coin!

The only summary information available at this moment is on the first page of this topic.  The coin was pump and dumped by the original dev, and it has a huge premine sitting around that we haven't been able to trace just yet. 

I'm fighting the QT libraries at the moment to get a new set of clients built and released for now - while I finish bringing the rest of the updates and fixes into the client from the other coins -- Once we get the client re-released with new SSL and checkpoints, we're going to try to offer some bounties to get some more places to accept it for use.  I'm also working out a couple other ideas in the back of my head for usage as well -- if you have any ideas, feel free to add to this topic until we get the new one and forums online on it's own site Smiley



MAKE YOUR SHITS WITH ANOTHER COIN!!!

Well you just freed up a bunch of my time.  Fuck you too.  You can say what ever you want.  Your actions and your treatment of this coin, and it's supporters with that post I guarantee just got you a coin worth jack shit.  I hope it drops to 0 now and gets dumped from the exchanges.

Peace out guys...  I'm done here.  I've vested too much time for a response like that.


ARE YOU A MORON??? MAKE YOUR SHITS WITH ANOTHER COIN!!! AND YOU GO FUCK ITSELF!

Unless you've got something constructive to add I suggest you stop posting on this thread.

This isn't your coin anymore. 

 Grin  Grin  Grin Will see...
member
Activity: 95
Merit: 10

Are there any XenCoin accepting sites at this moment? Is there an overview somewhere?
Except for the exchanges, obviously :-)

@thecarnie: Keep up the good work. Nice to see there is active development on this coin!

The only summary information available at this moment is on the first page of this topic.  The coin was pump and dumped by the original dev, and it has a huge premine sitting around that we haven't been able to trace just yet. 

I'm fighting the QT libraries at the moment to get a new set of clients built and released for now - while I finish bringing the rest of the updates and fixes into the client from the other coins -- Once we get the client re-released with new SSL and checkpoints, we're going to try to offer some bounties to get some more places to accept it for use.  I'm also working out a couple other ideas in the back of my head for usage as well -- if you have any ideas, feel free to add to this topic until we get the new one and forums online on it's own site Smiley



MAKE YOUR SHITS WITH ANOTHER COIN!!!

Well you just freed up a bunch of my time.  Fuck you too.  You can say what ever you want.  Your actions and your treatment of this coin, and it's supporters with that post I guarantee just got you a coin worth jack shit.  I hope it drops to 0 now and gets dumped from the exchanges.

Peace out guys...  I'm done here.  I've vested too much time for a response like that.


ARE YOU A MORON??? MAKE YOUR SHITS WITH ANOTHER COIN!!! AND YOU GO FUCK ITSELF!

Unless you've got something constructive to add I suggest you stop posting on this thread.

This isn't your coin anymore. 
member
Activity: 77
Merit: 10

Are there any XenCoin accepting sites at this moment? Is there an overview somewhere?
Except for the exchanges, obviously :-)

@thecarnie: Keep up the good work. Nice to see there is active development on this coin!

The only summary information available at this moment is on the first page of this topic.  The coin was pump and dumped by the original dev, and it has a huge premine sitting around that we haven't been able to trace just yet. 

I'm fighting the QT libraries at the moment to get a new set of clients built and released for now - while I finish bringing the rest of the updates and fixes into the client from the other coins -- Once we get the client re-released with new SSL and checkpoints, we're going to try to offer some bounties to get some more places to accept it for use.  I'm also working out a couple other ideas in the back of my head for usage as well -- if you have any ideas, feel free to add to this topic until we get the new one and forums online on it's own site Smiley



MAKE YOUR SHITS WITH ANOTHER COIN!!!

Well you just freed up a bunch of my time.  Fuck you too.  You can say what ever you want.  Your actions and your treatment of this coin, and it's supporters with that post I guarantee just got you a coin worth jack shit.  I hope it drops to 0 now and gets dumped from the exchanges.

Peace out guys...  I'm done here.  I've vested too much time for a response like that.


ARE YOU A MORON??? MAKE YOUR SHITS WITH ANOTHER COIN!!! AND YOU GO FUCK ITSELF!
legendary
Activity: 3570
Merit: 1126
I've returned Xencoin to the www.hasher.ca pool.

If there is anyone that wants to test it out, it seem to be working for me. Here is the info from the wallet that is synced on it and it looks to be good:

$ xencoind getinfo
{
    "version" : 80703,
    "protocolversion" : 70002,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 907226,
    "timeoffset" : -18,
    "connections" : 16,
    "proxy" : "",
    "difficulty" : 0.01164184,
    "testnet" : false,
    "keypoololdest" : 1406070927,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "errors" : ""
}
Pages:
Jump to: