Pages:
Author

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

legendary
Activity: 3486
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...



Ok good idea, I'll let them if/when they respond. Can sometimes take them a while... other times not...

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

full member
Activity: 136
Merit: 100
legendary
Activity: 3486
Merit: 1126
Got a QT client built for windows -- had to disable qrcode support for the moment in the config, but it popped up and connected to the network.

Anyone wish to test sending a couple XNC to XyuH7qjfAw4Q9n3Hc9iSonkKKpoAkibxDj

They will be send back in a round-robin test.  I'm looking for hopefully an old client and one from the new code if possible.  Thanks


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" : ""
}

Just noticed you've got 8 connections - i've only got one each on two active wallets  Sad

Any chance you could post your getpeerinfo so I can get some extra nodes please  Grin

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
}
member
Activity: 95
Merit: 10
Got a QT client built for windows -- had to disable qrcode support for the moment in the config, but it popped up and connected to the network.

Anyone wish to test sending a couple XNC to XyuH7qjfAw4Q9n3Hc9iSonkKKpoAkibxDj

They will be send back in a round-robin test.  I'm looking for hopefully an old client and one from the new code if possible.  Thanks


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" : ""
}

Just noticed you've got 8 connections - i've only got one each on two active wallets  Sad

Any chance you could post your getpeerinfo so I can get some extra nodes please  Grin
member
Activity: 95
Merit: 10
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!

yeah I did a test one today to see if they were on the right chain, but then noticed that it was offline. I just sent it to my known address before I checked...

I've got a ticket open too and had the same message.

I opened my ticket on the 6th July......
legendary
Activity: 3486
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!

yeah I did a test one today to see if they were on the right chain, but then noticed that it was offline. I just sent it to my known address before I checked...

I've got a ticket open too and had the same message.
member
Activity: 95
Merit: 10
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!
legendary
Activity: 3486
Merit: 1126
darn, also looks like Cryptsy has the wallet offline.
legendary
Activity: 3486
Merit: 1126
Got a QT client built for windows -- had to disable qrcode support for the moment in the config, but it popped up and connected to the network.

Anyone wish to test sending a couple XNC to XyuH7qjfAw4Q9n3Hc9iSonkKKpoAkibxDj

They will be send back in a round-robin test.  I'm looking for hopefully an old client and one from the new code if possible.  Thanks


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" : ""
}
full member
Activity: 136
Merit: 100
Got a QT client built for windows -- had to disable qrcode support for the moment in the config, but it popped up and connected to the network.

Anyone wish to test sending a couple XNC to XyuH7qjfAw4Q9n3Hc9iSonkKKpoAkibxDj

They will be send back in a round-robin test.  I'm looking for hopefully an old client and one from the new code if possible.  Thanks
full member
Activity: 136
Merit: 100
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 --
full member
Activity: 136
Merit: 100
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.




What boost version are you compiled with?  Any way you could send like the last 100 lines of the log over to me or post to Github as an issue so I can try to track it in the code?

full member
Activity: 136
Merit: 100
I have a miner mining 24/7 with a Xencoin wallet running all the time - this is fully synced at 899675 at the time of writing - will this show up as an active node and help the network or do I need to do anything else to make it do so? Should I open port 4334 on my router? If I did so would this have any security consequences? I don't store any coins in this wallet but do occasionally solo mine to it.

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 Smiley
full member
Activity: 136
Merit: 100
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.


I believe I might have an issue in the thread naming from the code-update -- because I'm getting an abnormal termination from the daemon on my win7 box too --

Were you able to get the chain downloaded in the old client?  xenseeder shows the older node up to date now --
legendary
Activity: 3486
Merit: 1126
ahh ok... here is where my windows client is stuck:

{
"blocks" : 854308,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 0.00686077,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 1560466,
"pooledtx" : 0,
"testnet" : false
}

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.
member
Activity: 95
Merit: 10
ahh ok... here is where my windows client is stuck:

{
"blocks" : 854308,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 0.00686077,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 1560466,
"pooledtx" : 0,
"testnet" : false
}

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.




I have a miner mining 24/7 with a Xencoin wallet running all the time - this is fully synced at 899675 at the time of writing - will this show up as an active node and help the network or do I need to do anything else to make it do so? Should I open port 4334 on my router? If I did so would this have any security consequences? I don't store any coins in this wallet but do occasionally solo mine to it.
full member
Activity: 136
Merit: 100
ahh ok... here is where my windows client is stuck:

{
"blocks" : 854308,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 0.00686077,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 1560466,
"pooledtx" : 0,
"testnet" : false
}

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.

legendary
Activity: 3486
Merit: 1126
Xencoin Community Fork - Repo updated - checkpoints added - version data changed - https://github.com/thecarnie/xencoin (TESTING - UNSTABLE)
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+

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

ahh ok... here is where my windows client is stuck:

{
"blocks" : 854308,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 0.00686077,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 1560466,
"pooledtx" : 0,
"testnet" : false
}
full member
Activity: 136
Merit: 100
Xencoin Community Fork - Repo updated - checkpoints added - version data changed - https://github.com/thecarnie/xencoin (TESTING - UNSTABLE)
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+

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
Pages:
Jump to: