Onyf
Member
Offline
Activity: 84
Merit: 10
|
|
August 14, 2017, 11:58:49 AM |
|
Pool Hempcoin Fee 2% No registration Auto payments 30 min Large selection of coins and algorithms
http://TimeTeh.com/
|
|
|
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
reffi
|
|
August 21, 2017, 04:19:56 PM |
|
I just bought 1 million THC! Lets make this happen, Moooooooooon Time!!!!!!
|
|
|
|
VelureBit
|
|
August 23, 2017, 12:13:54 PM |
|
I find it ironic that hemp has virtually no THC in it, yet you're use the initials THC.
brilliant, dude
|
|
|
|
VelureBit
|
|
August 23, 2017, 12:19:58 PM |
|
LET's GO THC COIN!!! WE NEED ED WE NEED
|
|
|
|
CryptoKeeper802
|
|
August 23, 2017, 02:16:51 PM |
|
I'm trying to get my Hempcoin desktop wallet working again, as for some reason it went out of sync... I used the bootstrap file you guys made back in November of 2016 and the blockchain is redownloading right now... but I only have 1 active connection on the network, there should be more... Is there some special file I need to add nodes / connections?
|
|
|
|
Joint Force
|
|
August 23, 2017, 02:33:06 PM Last edit: August 23, 2017, 02:53:56 PM by Joint Force |
|
I'm trying to get my Hempcoin desktop wallet working again, as for some reason it went out of sync... I used the bootstrap file you guys made back in November of 2016 and the blockchain is redownloading right now... but I only have 1 active connection on the network, there should be more... Is there some special file I need to add nodes / connections?
https://bittrex.com/StatusShows 6 connections. Unfortunately the block explorer, where a node list existed, died. Does anyone know how to get on https://chainz.cryptoid.info ? THC is a high quality coin that should be listed there. THC is listed on bittrex and coinomi. It doesn't get much better than that. Getting on cryptoid would be a perfect addition. Then there would be a place to go and find working addnodes.
|
|
|
|
groggin
Legendary
Offline
Activity: 1894
Merit: 1001
|
|
August 23, 2017, 04:50:23 PM |
|
I'm trying to get my Hempcoin desktop wallet working again, as for some reason it went out of sync... I used the bootstrap file you guys made back in November of 2016 and the blockchain is redownloading right now... but I only have 1 active connection on the network, there should be more... Is there some special file I need to add nodes / connections?
here's a copy of my hempcoin.conf: addnode=24.253.102.174 addnode=129.21.131.213 addnode=75.130.183.104 addnode=82.181.124.248 addnode=104.131.16.240 addnode=115.236.88.86 addnode=69.10.58.157 addnode=198.27.106.7 addnode=162.243.1.45 addnode=162.209.109.81 addnode=83.183.247.151 addnode=24.69.200.51 addnode=82.21.238.186 addnode=54.186.62.109 addnode=88.208.236.108 addnode=198.50.132.65 addnode=69.10.58.157 rpcport=12055 here's a list of nodes i have connected right now. to get them into your wallet, open the hempcoin data folder and open for editing the hempcoin.conf file. (create one if it doesn't exist) then parse this list below for the ip addys and add them to the .conf. then restart your wallet 12:43:04  getpeerinfo
12:43:04  [ { "addr" : "217.61.5.15:21054", "services" : "00000001", "lastsend" : 1503506556, "lastrecv" : 1503506556, "conntime" : 1503496450, "version" : 80020, "subver" : "/Satoshi:2.0.0.1/", "inbound" : false, "releasetime" : 0, "startingheight" : 1745712, "banscore" : 0 }, { "addr" : "138.201.39.53:21054", "services" : "00000001", "lastsend" : 1503506556, "lastrecv" : 1503506538, "conntime" : 1503496478, "version" : 80020, "subver" : "/Satoshi:2.0.0.1/", "inbound" : false, "releasetime" : 0, "startingheight" : 1745712, "banscore" : 0 }, { "addr" : "31.31.78.40:21054", "services" : "00000001", "lastsend" : 1503506538, "lastrecv" : 1503506554, "conntime" : 1503496746, "version" : 80020, "subver" : "/Satoshi:2.0.0.1/", "inbound" : false, "releasetime" : 0, "startingheight" : 1745718, "banscore" : 0 }, { "addr" : "5.9.10.66:21054", "services" : "00000001", "lastsend" : 1503505507, "lastrecv" : 1503506425, "conntime" : 1503496873, "version" : 80020, "subver" : "/Satoshi:2.0.0.1/", "inbound" : false, "releasetime" : 0, "startingheight" : 1745721, "banscore" : 0 }, { "addr" : "138.68.108.250:21054", "services" : "00000001", "lastsend" : 1503505507, "lastrecv" : 1503506425, "conntime" : 1503497057, "version" : 80020, "subver" : "/Satoshi:2.0.0.1/", "inbound" : false, "releasetime" : 0, "startingheight" : 1745725, "banscore" : 0 }, { "addr" : "115.236.88.86:21054", "services" : "00000001", "lastsend" : 1503506324, "lastrecv" : 1503506426, "conntime" : 1503498559, "version" : 80020, "subver" : "/Satoshi:2.0.0.1/", "inbound" : false, "releasetime" : 0, "startingheight" : 1745753, "banscore" : 0 } ]
|
|
|
|
zecon
Full Member
Offline
Activity: 364
Merit: 100
spattered throughout the golden ethers
|
|
August 23, 2017, 05:57:25 PM |
|
I just bought 1 million THC! Lets make this happen, Moooooooooon Time!!!!!! Any particular reason you picked up 1m? Or just shilling?
|
If you really want to do something, you’ll find a way. If you don’t, you’ll find an excuse. — Jim Rohn
|
|
|
CryptoKeeper802
|
|
August 23, 2017, 06:11:16 PM |
|
So all I have to do is copy the following code into the hempcoin.conf [or make one out of a txt document] and put the following code in and restart wallet? 12:43:04  getpeerinfo
12:43:04  [ { "addr" : "217.61.5.15:21054", "services" : "00000001", "lastsend" : 1503506556, "lastrecv" : 1503506556, "conntime" : 1503496450, "version" : 80020, "subver" : "/Satoshi:2.0.0.1/", "inbound" : false, "releasetime" : 0, "startingheight" : 1745712, "banscore" : 0 }, { "addr" : "138.201.39.53:21054", "services" : "00000001", "lastsend" : 1503506556, "lastrecv" : 1503506538, "conntime" : 1503496478, "version" : 80020, "subver" : "/Satoshi:2.0.0.1/", "inbound" : false, "releasetime" : 0, "startingheight" : 1745712, "banscore" : 0 }, { "addr" : "31.31.78.40:21054", "services" : "00000001", "lastsend" : 1503506538, "lastrecv" : 1503506554, "conntime" : 1503496746, "version" : 80020, "subver" : "/Satoshi:2.0.0.1/", "inbound" : false, "releasetime" : 0, "startingheight" : 1745718, "banscore" : 0 }, { "addr" : "5.9.10.66:21054", "services" : "00000001", "lastsend" : 1503505507, "lastrecv" : 1503506425, "conntime" : 1503496873, "version" : 80020, "subver" : "/Satoshi:2.0.0.1/", "inbound" : false, "releasetime" : 0, "startingheight" : 1745721, "banscore" : 0 }, { "addr" : "138.68.108.250:21054", "services" : "00000001", "lastsend" : 1503505507, "lastrecv" : 1503506425, "conntime" : 1503497057, "version" : 80020, "subver" : "/Satoshi:2.0.0.1/", "inbound" : false, "releasetime" : 0, "startingheight" : 1745725, "banscore" : 0 }, { "addr" : "115.236.88.86:21054", "services" : "00000001", "lastsend" : 1503506324, "lastrecv" : 1503506426, "conntime" : 1503498559, "version" : 80020, "subver" : "/Satoshi:2.0.0.1/", "inbound" : false, "releasetime" : 0, "startingheight" : 1745753, "banscore" : 0 } ] I'm trying to get my Hempcoin desktop wallet working again, as for some reason it went out of sync... I used the bootstrap file you guys made back in November of 2016 and the blockchain is redownloading right now... but I only have 1 active connection on the network, there should be more... Is there some special file I need to add nodes / connections?
here's a copy of my hempcoin.conf: addnode=24.253.102.174 addnode=129.21.131.213 addnode=75.130.183.104 addnode=82.181.124.248 addnode=104.131.16.240 addnode=115.236.88.86 addnode=69.10.58.157 addnode=198.27.106.7 addnode=162.243.1.45 addnode=162.209.109.81 addnode=83.183.247.151 addnode=24.69.200.51 addnode=82.21.238.186 addnode=54.186.62.109 addnode=88.208.236.108 addnode=198.50.132.65 addnode=69.10.58.157 rpcport=12055 here's a list of nodes i have connected right now. to get them into your wallet, open the hempcoin data folder and open for editing the hempcoin.conf file. (create one if it doesn't exist) then parse this list below for the ip addys and add them to the .conf. then restart your wallet 12:43:04  getpeerinfo
12:43:04  [ { "addr" : "217.61.5.15:21054", "services" : "00000001", "lastsend" : 1503506556, "lastrecv" : 1503506556, "conntime" : 1503496450, "version" : 80020, "subver" : "/Satoshi:2.0.0.1/", "inbound" : false, "releasetime" : 0, "startingheight" : 1745712, "banscore" : 0 }, { "addr" : "138.201.39.53:21054", "services" : "00000001", "lastsend" : 1503506556, "lastrecv" : 1503506538, "conntime" : 1503496478, "version" : 80020, "subver" : "/Satoshi:2.0.0.1/", "inbound" : false, "releasetime" : 0, "startingheight" : 1745712, "banscore" : 0 }, { "addr" : "31.31.78.40:21054", "services" : "00000001", "lastsend" : 1503506538, "lastrecv" : 1503506554, "conntime" : 1503496746, "version" : 80020, "subver" : "/Satoshi:2.0.0.1/", "inbound" : false, "releasetime" : 0, "startingheight" : 1745718, "banscore" : 0 }, { "addr" : "5.9.10.66:21054", "services" : "00000001", "lastsend" : 1503505507, "lastrecv" : 1503506425, "conntime" : 1503496873, "version" : 80020, "subver" : "/Satoshi:2.0.0.1/", "inbound" : false, "releasetime" : 0, "startingheight" : 1745721, "banscore" : 0 }, { "addr" : "138.68.108.250:21054", "services" : "00000001", "lastsend" : 1503505507, "lastrecv" : 1503506425, "conntime" : 1503497057, "version" : 80020, "subver" : "/Satoshi:2.0.0.1/", "inbound" : false, "releasetime" : 0, "startingheight" : 1745725, "banscore" : 0 }, { "addr" : "115.236.88.86:21054", "services" : "00000001", "lastsend" : 1503506324, "lastrecv" : 1503506426, "conntime" : 1503498559, "version" : 80020, "subver" : "/Satoshi:2.0.0.1/", "inbound" : false, "releasetime" : 0, "startingheight" : 1745753, "banscore" : 0 } ]
|
|
|
|
groggin
Legendary
Offline
Activity: 1894
Merit: 1001
|
|
August 23, 2017, 07:13:00 PM |
|
So all I have to do is copy the following code into the hempcoin.conf [or make one out of a txt document] and put the following code in and restart wallet?
no... that's the command i used to get the info you need to parse the list for the IPs example: 12:43:04  getpeerinfo 12:43:04  [ { "addr" : " 217.61.5.15:21054", "services" : "00000001", "lastsend" : 1503506556, "lastrecv" : 1503506556, take the address:port (highlighted) and put it in a line in the .conf: addnode=217.61.5.15:21054 there are 6 of these to add in the second list, above -as in the example, above it
|
|
|
|
CryptoKeeper802
|
|
August 23, 2017, 08:31:10 PM Last edit: August 23, 2017, 08:56:51 PM by CryptoKeeper802 |
|
I tried parsing the list and made a hempcoin.conf file that contains the following: addnode=217.61.5.15 addnode=138.201.39.53 addnode=31.31.78.40 addnode=5.9.10.66 addnode=138.68.108.250 addnode=15.236.88.86 rpcport=21054 When I turn the wallet on it says that it's rescanning, then eventually opens the wallet and there are still zero connections to the hempcoin network and it's not progressing to sync anymore. What do I do? So all I have to do is copy the following code into the hempcoin.conf [or make one out of a txt document] and put the following code in and restart wallet?
no... that's the command i used to get the info you need to parse the list for the IPs example: 12:43:04  getpeerinfo 12:43:04  [ { "addr" : " 217.61.5.15:21054", "services" : "00000001", "lastsend" : 1503506556, "lastrecv" : 1503506556, take the address:port (highlighted) and put it in a line in the .conf: addnode=217.61.5.15:21054 there are 6 of these to add in the second list, above -as in the example, above it
|
|
|
|
Joint Force
|
|
August 24, 2017, 04:09:04 AM |
|
I tried parsing the list and made a hempcoin.conf file that contains the following: addnode=217.61.5.15 addnode=138.201.39.53 addnode=31.31.78.40 addnode=5.9.10.66 addnode=138.68.108.250 addnode=15.236.88.86 rpcport=21054 When I turn the wallet on it says that it's rescanning, then eventually opens the wallet and there are still zero connections to the hempcoin network and it's not progressing to sync anymore. What do I do? You might need to also have rpcuser=xUniqueUserNamex rpcpassword=xUniquePasswordx in the .conf file and the addnodes should appear like this, include the ipaddress and port addnode=31.31.78.40:21054 addnode=138.201.39.53:21054 etc.
|
|
|
|
groggin
Legendary
Offline
Activity: 1894
Merit: 1001
|
|
August 24, 2017, 04:43:06 AM |
|
^^you might also check (are you using windows?) to make sure that your firewall is allowing connections
|
|
|
|
CryptoKeeper802
|
|
August 24, 2017, 05:29:13 AM |
|
^^you might also check (are you using windows?) to make sure that your firewall is allowing connections
Yes I am using windows and have staking happening successfully on other wallets, so it can't be a firewall issue.
|
|
|
|
CryptoKeeper802
|
|
August 24, 2017, 05:32:07 AM |
|
Okay that is maybe what I was doing wrong last time. More questions... 1. Am I putting the correct number for the rpcport? I was just guessing it was the number at the end of the IP addresses. Should I copy the number from your file example? 2. rpcuser=xUniqueUserNamex rpcpassword=xUniquePasswordx would I put these entries under the rpcport? AND for the xUniqueUserNamex and xUniquePasswordx... where do I come up with this info? Or do I enter it as you have shown? I tried parsing the list and made a hempcoin.conf file that contains the following: addnode=217.61.5.15 addnode=138.201.39.53 addnode=31.31.78.40 addnode=5.9.10.66 addnode=138.68.108.250 addnode=15.236.88.86 rpcport=21054 When I turn the wallet on it says that it's rescanning, then eventually opens the wallet and there are still zero connections to the hempcoin network and it's not progressing to sync anymore. What do I do? You might need to also have rpcuser=xUniqueUserNamex rpcpassword=xUniquePasswordx in the .conf file and the addnodes should appear like this, include the ipaddress and port addnode=31.31.78.40:21054 addnode=138.201.39.53:21054 etc.
|
|
|
|
groggin
Legendary
Offline
Activity: 1894
Merit: 1001
|
|
August 24, 2017, 06:24:46 AM |
|
2. rpcuser=xUniqueUserNamex rpcpassword=xUniquePasswordx
would I put these entries under the rpcport? i did it for you. you can use this as is, or feel free to change the username and password copy-paste into a text file 'hempcoin.conf' in the data directory addnode=217.61.5.15:21054 addnode=138.201.39.53:21054 addnode=115.236.88.86:2105 addnode=31.31.78.40:21054 addnode=5.9.10.66:21054 addnode=138.68.108.250:21054 rpcport=12055 rpcuser=xUniqueUserNamex rpcpassword=xUniquePasswordx
|
|
|
|
CryptoKeeper802
|
|
August 24, 2017, 07:20:36 AM |
|
Thank you I appreciate that. I copy and pasted this into the hempcoin.conf txt file that is in the root directory of the Hempcoin appdata folder, and saved it. When reloading the wallet, I still have zero connections. I did not update anything in the username or password fields... is there something I should put there? It doesn't actually want the wallet password does it? That would seem insecure... not sure where the username would actually come from. Do I need to do a new wallet download? maybe it's broken? 2. rpcuser=xUniqueUserNamex rpcpassword=xUniquePasswordx
would I put these entries under the rpcport? i did it for you. you can use this as is, or feel free to change the username and password copy-paste into a text file 'hempcoin.conf' in the data directory addnode=217.61.5.15:21054 addnode=138.201.39.53:21054 addnode=115.236.88.86:2105 addnode=31.31.78.40:21054 addnode=5.9.10.66:21054 addnode=138.68.108.250:21054 rpcport=12055 rpcuser=xUniqueUserNamex rpcpassword=xUniquePasswordx
|
|
|
|
groggin
Legendary
Offline
Activity: 1894
Merit: 1001
|
|
August 24, 2017, 12:13:44 PM Last edit: August 24, 2017, 12:31:42 PM by groggin |
|
if you're using wallet v2.0.0.1, i'd just let it run for a while, it should hook up. if not, then retry the dl you can also look at the .log file, the last few hundred lines will do their own explaining [help]>[information tab]>[open] debug log file the user/pass thing is optional unless you plan to solo mine, or otherwise use RPC, in which case you should create your own unique and difficult to guess inputs Oh! maybe you made a common mistake: I copy and pasted this into the hempcoin.conf txt file that is in the root directory of the Hempcoin appdata folder pls check and make sure the conf file is named hempcoin.conf, not hempcoin.conf.txt, which may be the result if you're not careful in windows be sure to restart the wallet after making any changes to the .conf
|
|
|
|
CryptoKeeper802
|
|
August 24, 2017, 03:47:33 PM |
|
Pretty sure I got the file correct for the hempcoin.conf, here is an image: Just noticed I'm on wallet v.2.0.0.0 [is that maybe the problem?] Here is what my log reported [I had to erase most of the beginning of it so it would fit here]: connection timeout trying connection 79.168.193.22:21054 lastseen=10.9hrs connection timeout trying connection 173.208.164.34:21054 lastseen=18.9hrs connection timeout trying connection 173.208.164.34:21054 lastseen=18.9hrs connection timeout trying connection 79.168.193.22:21054 lastseen=10.9hrs connection timeout trying connection 173.208.164.34:21054 lastseen=18.9hrs connection timeout trying connection 183.232.175.4:21054 lastseen=112.4hrs connection timeout trying connection 88.23.78.16:21054 lastseen=8.2hrs connection timeout trying connection 79.168.193.22:21054 lastseen=10.9hrs connection timeout trying connection 173.208.164.34:21054 lastseen=18.9hrs connection timeout trying connection 79.168.193.22:21054 lastseen=10.9hrs connection timeout trying connection 97.113.72.250:21054 lastseen=8.2hrs connection timeout trying connection 79.168.193.22:21054 lastseen=10.9hrs connection timeout trying connection 79.168.193.22:21054 lastseen=10.9hrs connection timeout trying connection 79.168.193.22:21054 lastseen=10.9hrs connection timeout trying connection 178.89.201.232:21054 lastseen=10.6hrs connection timeout trying connection 79.168.193.22:21054 lastseen=10.9hrs connection timeout trying connection 79.168.193.22:21054 lastseen=10.9hrs IRC got join connection timeout trying connection 79.168.193.22:21054 lastseen=10.9hrs connection timeout trying connection 79.168.193.22:21054 lastseen=10.9hrs connection timeout trying connection 173.208.164.34:21054 lastseen=18.9hrs connection timeout trying connection 173.208.164.34:21054 lastseen=18.9hrs connection timeout trying connection 79.168.193.22:21054 lastseen=10.9hrs connection timeout trying connection 173.208.164.34:21054 lastseen=18.9hrs connection timeout trying connection 79.168.193.22:21054 lastseen=10.9hrs connection timeout trying connection 173.208.164.34:21054 lastseen=18.9hrs connection timeout trying connection 173.208.164.34:21054 lastseen=18.9hrs connection timeout trying connection 173.208.164.34:21054 lastseen=18.9hrs connection timeout trying connection 65.35.19.226:21054 lastseen=2.4hrs connection timeout trying connection 79.168.193.22:21054 lastseen=10.9hrs IRC got join Added 90.11.171.242:21054 from 2001:bc8:315e:303::1: 2 tried, 64 new IRC got new address: 90.11.171.242:21054 connection timeout trying connection 173.208.164.34:21054 lastseen=18.9hrs connection timeout trying connection 79.168.193.22:21054 lastseen=10.9hrs connection timeout trying connection 79.168.193.22:21054 lastseen=10.9hrs connection timeout trying connection 88.23.78.16:21054 lastseen=8.2hrs connection timeout trying connection 173.208.164.34:21054 lastseen=18.9hrs connection timeout trying connection 173.208.164.34:21054 lastseen=18.9hrs connection timeout trying connection 79.168.193.22:21054 lastseen=10.9hrs connection timeout trying connection 79.168.193.22:21054 lastseen=10.9hrs connection timeout trying connection 79.168.193.22:21054 lastseen=10.9hrs connection timeout trying connection 173.208.164.34:21054 lastseen=18.9hrs connection timeout trying connection 79.168.193.22:21054 lastseen=10.9hrs connection timeout trying connection 173.208.164.34:21054 lastseen=18.9hrs connection timeout trying connection 79.168.193.22:21054 lastseen=10.9hrs connection timeout trying connection 42.112.88.241:21054 lastseen=4.9hrs connection timeout trying connection 173.208.164.34:21054 lastseen=18.9hrs connection timeout trying connection 79.168.193.22:21054 lastseen=10.9hrs connection timeout trying connection 31.172.200.175:21054 lastseen=8.3hrs connection timeout trying connection 79.168.193.22:21054 lastseen=10.9hrs connection timeout trying connection 42.112.88.241:21054 lastseen=4.9hrs connection timeout trying connection 181.41.15.111:21054 lastseen=25.7hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=10.9hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.0hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.0hrs connection timeout trying connection 93.208.84.236:21054 lastseen=5.5hrs connection timeout trying connection 79.168.193.22:21054 lastseen=10.9hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.0hrs connection timeout trying connection 78.251.112.84:21054 lastseen=26.1hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.0hrs connection timeout trying connection 178.89.201.232:21054 lastseen=10.7hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.0hrs connection timeout trying connection 79.246.227.179:21054 lastseen=11.3hrs connection timeout trying connection 98.180.124.103:21054 lastseen=8.3hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.0hrs connection timeout trying connection 31.172.200.175:21054 lastseen=8.3hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.0hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.0hrs connection timeout trying connection 73.79.240.65:21054 lastseen=8.3hrs connection timeout trying connection 42.112.88.241:21054 lastseen=5.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.0hrs connection timeout trying connection 90.11.171.242:21054 lastseen=0.9hrs connection timeout trying connection 93.208.84.236:21054 lastseen=5.5hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.0hrs connection timeout trying connection 81.158.177.220:21054 lastseen=1.6hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.0hrs connection timeout trying connection 81.158.177.220:21054 lastseen=1.6hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.0hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.0hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.0hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.0hrs connection timeout trying connection 79.246.227.179:21054 lastseen=11.3hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.0hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.0hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.0hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.0hrs connection timeout Flushed 66 addresses to peers.dat 20ms trying connection 173.208.164.34:21054 lastseen=19.0hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.0hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.0hrs connection timeout trying connection 173.239.232.58:21054 lastseen=8.4hrs connection timeout trying connection 90.11.171.242:21054 lastseen=1.0hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.0hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.0hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.0hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.1hrs connection timeout trying connection 65.35.19.226:21054 lastseen=2.5hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.0hrs connection timeout trying connection 14.163.119.75:21054 lastseen=1.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.0hrs connection timeout trying connection 88.23.78.16:21054 lastseen=8.4hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.1hrs connection timeout trying connection 73.79.240.65:21054 lastseen=8.4hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.1hrs connection timeout trying connection 14.163.119.75:21054 lastseen=1.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.1hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.1hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.1hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.1hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.1hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.1hrs connection timeout trying connection 14.163.119.75:21054 lastseen=1.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.1hrs connection timeout trying connection 138.197.199.5:21054 lastseen=8.4hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.1hrs connection timeout trying connection 65.35.19.226:21054 lastseen=2.5hrs connection timeout trying connection 73.79.240.65:21054 lastseen=8.4hrs connection timeout trying connection 65.35.19.226:21054 lastseen=2.5hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.1hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.1hrs connection timeout trying connection 47.72.252.205:21054 lastseen=8.4hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.1hrs connection timeout trying connection 88.23.78.16:21054 lastseen=8.4hrs connection timeout trying connection 93.208.84.236:21054 lastseen=5.6hrs connection timeout trying connection 65.35.19.226:21054 lastseen=2.5hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.1hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.1hrs connection timeout trying connection 73.79.240.65:21054 lastseen=8.4hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.1hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.1hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.1hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.1hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.1hrs connection timeout trying connection 98.180.124.103:21054 lastseen=8.4hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.1hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.1hrs connection timeout trying connection 73.79.240.65:21054 lastseen=8.4hrs connection timeout trying connection 88.23.78.16:21054 lastseen=8.4hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.1hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.1hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.1hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.1hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.1hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.1hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.1hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.1hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.1hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.1hrs connection timeout trying connection 65.35.19.226:21054 lastseen=2.6hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.1hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.1hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.1hrs connection timeout trying connection 81.158.177.220:21054 lastseen=1.7hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.1hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.1hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.1hrs connection timeout trying connection 88.23.78.16:21054 lastseen=8.5hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.1hrs connection timeout trying connection 65.35.19.226:21054 lastseen=2.6hrs connection timeout trying connection 65.35.19.226:21054 lastseen=2.6hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.1hrs connection timeout trying connection 47.184.6.129:21054 lastseen=8.5hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.1hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.2hrs connection timeout trying connection 90.11.171.242:21054 lastseen=1.1hrs connection timeout trying connection 138.68.108.250:21054 lastseen=8.5hrs connected 138.68.108.250:21054 send version message: version 80014, blocks=769005, us=174.63.23.68:21054, them=138.68.108.250:21054, peer=138.68.108.250:21054 socket closed disconnecting node 138.68.108.250:21054 trying connection 173.239.232.58:21054 lastseen=8.5hrs connection timeout trying connection 88.23.78.16:21054 lastseen=8.5hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.1hrs connection timeout trying connection 73.79.240.65:21054 lastseen=8.5hrs connection timeout trying connection 108.240.79.108:21054 lastseen=19.1hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.2hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.2hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.2hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.2hrs connection timeout trying connection 65.35.19.226:21054 lastseen=2.6hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.2hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.2hrs connection timeout trying connection 66.25.172.234:21054 lastseen=15.5hrs connection timeout trying connection 65.35.19.226:21054 lastseen=2.6hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.2hrs connection timeout trying connection 93.208.84.236:21054 lastseen=5.7hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.2hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.2hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.2hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.2hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.2hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.2hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.2hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.2hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.2hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.2hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.2hrs connection timeout trying connection 65.35.19.226:21054 lastseen=2.6hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.2hrs Flushed 66 addresses to peers.dat 39ms connection timeout trying connection 79.168.193.22:21054 lastseen=11.2hrs connection timeout trying connection 78.251.112.84:21054 lastseen=26.3hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.2hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.2hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.2hrs connection timeout trying connection 162.243.1.45:21054 lastseen=95.3hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.2hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.2hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.2hrs connection timeout trying connection 81.158.177.220:21054 lastseen=1.8hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.2hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.2hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.2hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.2hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.2hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.2hrs connection timeout trying connection 98.180.124.103:21054 lastseen=8.5hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.2hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.2hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.2hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.2hrs connection timeout trying connection 138.197.199.5:21054 lastseen=8.5hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.2hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.2hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.2hrs connection timeout trying connection 97.113.72.250:21054 lastseen=8.6hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.2hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.2hrs connection timeout trying connection 81.158.177.220:21054 lastseen=1.8hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.2hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.2hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.3hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.2hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.2hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.3hrs connection timeout trying connection 45.63.78.209:21054 lastseen=8.6hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.3hrs connection timeout trying connection 93.208.84.236:21054 lastseen=5.8hrs connection timeout trying connection 88.23.78.16:21054 lastseen=8.6hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.3hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.3hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.3hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.3hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.3hrs connection timeout trying connection 70.54.164.50:21054 lastseen=8.6hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.3hrs connection timeout trying connection 181.41.15.111:21054 lastseen=26.1hrs connection timeout trying connection 178.89.201.232:21054 lastseen=11.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.3hrs connection timeout trying connection 65.35.19.226:21054 lastseen=2.7hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.3hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.3hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.3hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.3hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.3hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.3hrs connection timeout trying connection 81.158.177.220:21054 lastseen=1.8hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.3hrs connection timeout trying connection 78.56.87.109:21054 lastseen=16.4hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.3hrs connection timeout trying connection 183.232.175.3:21054 lastseen=40.6hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.3hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.3hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.3hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.3hrs connection timeout trying connection 90.11.171.242:21054 lastseen=1.2hrs connection timeout trying connection 73.79.240.65:21054 lastseen=8.6hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.3hrs connection timeout trying connection 81.158.177.220:21054 lastseen=1.9hrs connection timeout trying connection 90.11.171.242:21054 lastseen=1.2hrs connection timeout trying connection 88.23.78.16:21054 lastseen=8.6hrs connection timeout trying connection 98.180.124.103:21054 lastseen=8.6hrs connection timeout trying connection 202.92.146.168:21054 lastseen=8.6hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.3hrs connection timeout trying connection 202.92.146.168:21054 lastseen=8.6hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.3hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.3hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.3hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.3hrs connection timeout trying connection 59.167.119.80:21054 lastseen=26.4hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.3hrs IRC got join connection timeout trying connection 79.168.193.22:21054 lastseen=11.3hrs connection timeout trying connection 97.113.72.250:21054 lastseen=8.6hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.3hrs connection timeout trying connection 178.89.201.232:21054 lastseen=0.9hrs connection timeout trying connection 96.246.242.21:21054 lastseen=8.6hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.3hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.3hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.3hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.3hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.3hrs connection timeout trying connection 98.180.124.103:21054 lastseen=8.7hrs connection timeout trying connection 93.208.84.236:21054 lastseen=5.9hrs connection timeout trying connection 45.63.78.209:21054 lastseen=8.7hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.3hrs connection timeout trying connection 96.246.242.21:21054 lastseen=8.7hrs connection timeout trying connection 81.158.177.220:21054 lastseen=1.9hrs connection timeout trying connection 81.158.177.220:21054 lastseen=1.9hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.3hrs connection timeout trying connection 178.89.201.232:21054 lastseen=0.9hrs connection timeout trying connection 79.246.227.179:21054 lastseen=11.7hrs connection timeout trying connection 98.148.151.248:21054 lastseen=115.7hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.3hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.4hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.3hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.4hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.4hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.4hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.4hrs Flushed 66 addresses to peers.dat 160ms connection timeout trying connection 79.168.193.22:21054 lastseen=11.4hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.4hrs connection timeout trying connection 90.11.171.242:21054 lastseen=1.3hrs connection timeout trying connection 178.89.201.232:21054 lastseen=0.9hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.4hrs connection timeout trying connection 93.208.84.236:21054 lastseen=5.9hrs connection timeout trying connection 65.35.19.226:21054 lastseen=2.8hrs connection timeout trying connection 45.63.78.209:21054 lastseen=8.7hrs connection timeout trying connection 81.158.177.220:21054 lastseen=1.9hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.4hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.4hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.4hrs connection timeout trying connection 65.35.19.226:21054 lastseen=2.8hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.4hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.4hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.4hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.4hrs connection timeout trying connection 78.56.87.109:21054 lastseen=16.5hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.4hrs connection timeout trying connection 89.136.40.211:21054 lastseen=26.5hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.4hrs connection timeout trying connection 47.72.252.205:21054 lastseen=8.7hrs connection timeout trying connection 96.246.242.21:21054 lastseen=8.7hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.4hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.4hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.4hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.4hrs connection timeout trying connection 42.112.88.241:21054 lastseen=5.4hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.4hrs connection timeout trying connection 173.239.232.58:21054 lastseen=8.7hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.4hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.4hrs connection timeout trying connection 47.72.252.205:21054 lastseen=8.7hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.4hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.4hrs connection timeout trying connection 178.89.201.232:21054 lastseen=0.9hrs connection timeout trying connection 173.239.232.58:21054 lastseen=8.7hrs connection timeout trying connection 73.79.240.65:21054 lastseen=8.7hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.4hrs connection timeout trying connection 81.158.177.220:21054 lastseen=2.0hrs connection timeout trying connection 45.63.78.209:21054 lastseen=8.7hrs connection timeout trying connection 162.243.1.45:21054 lastseen=95.6hrs connection timeout trying connection 178.89.201.232:21054 lastseen=1.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.4hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.4hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.4hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.4hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.4hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.4hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.4hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.4hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.4hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.4hrs connection timeout trying connection 202.92.146.168:21054 lastseen=8.8hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.5hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.5hrs connection timeout trying connection 88.23.78.16:21054 lastseen=8.8hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.5hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.4hrs connection timeout trying connection 178.89.201.232:21054 lastseen=1.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.4hrs connection timeout trying connection 138.197.199.5:21054 lastseen=8.8hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.5hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.5hrs connection timeout trying connection 178.89.201.232:21054 lastseen=1.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.5hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.5hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.5hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.5hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.5hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.5hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.5hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.5hrs connection timeout trying connection 178.89.201.232:21054 lastseen=1.0hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.5hrs IRC got join Added 108.4.210.169:21054 from 2001:bc8:315e:303::1: 2 tried, 65 new IRC got new address: 108.4.210.169:21054 connection timeout trying connection 79.168.193.22:21054 lastseen=11.5hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.5hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.5hrs connection timeout trying connection 178.89.201.232:21054 lastseen=1.0hrs connection timeout trying connection 96.246.242.21:21054 lastseen=8.8hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.5hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.5hrs connection timeout trying connection 65.35.19.226:21054 lastseen=2.9hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.5hrs connection timeout trying connection 78.56.87.109:21054 lastseen=16.6hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.5hrs connection timeout trying connection 138.197.199.5:21054 lastseen=8.8hrs connection timeout trying connection 98.180.124.103:21054 lastseen=8.8hrs connection timeout trying connection 81.158.177.220:21054 lastseen=2.1hrs connection timeout trying connection 108.4.210.169:21054 lastseen=0.9hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.5hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.5hrs connection timeout trying connection 138.197.199.5:21054 lastseen=8.8hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.5hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.5hrs connection timeout trying connection 178.89.201.232:21054 lastseen=1.0hrs connection timeout trying connection 138.197.199.5:21054 lastseen=8.8hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.5hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.5hrs connection timeout trying connection 178.89.201.232:21054 lastseen=1.0hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.5hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.5hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.5hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.5hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.5hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.5hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.5hrs connection timeout trying connection 108.4.210.169:21054 lastseen=0.9hrs connection timeout trying connection 98.148.151.248:21054 lastseen=115.8hrs Flushed 67 addresses to peers.dat 40ms connection timeout trying connection 138.197.199.5:21054 lastseen=8.9hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.5hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.5hrs connection timeout trying connection 98.180.124.103:21054 lastseen=8.9hrs connection timeout trying connection 108.4.210.169:21054 lastseen=0.9hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.5hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.5hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.5hrs connection timeout trying connection 65.35.19.226:21054 lastseen=3.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.5hrs connection timeout trying connection 65.35.19.226:21054 lastseen=3.0hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.6hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.6hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.6hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.6hrs connection timeout trying connection 178.89.201.232:21054 lastseen=1.1hrs connection timeout trying connection 178.89.201.232:21054 lastseen=1.1hrs connection timeout trying connection 173.239.232.58:21054 lastseen=8.9hrs connection timeout trying connection 97.113.72.250:21054 lastseen=8.9hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.6hrs connection timeout trying connection 14.163.119.75:21054 lastseen=1.5hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.6hrs connection timeout IRC got join trying connection 79.168.193.22:21054 lastseen=11.6hrs connection timeout trying connection 78.56.87.109:21054 lastseen=16.7hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.6hrs connection timeout trying connection 178.89.201.232:21054 lastseen=1.1hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.6hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.6hrs connection timeout trying connection 14.163.119.75:21054 lastseen=1.5hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.6hrs connection timeout trying connection 108.4.210.169:21054 lastseen=0.9hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.6hrs connection timeout trying connection 108.4.210.169:21054 lastseen=1.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.6hrs connection timeout trying connection 98.180.124.103:21054 lastseen=8.9hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.6hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.6hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.6hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.6hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.6hrs connection timeout trying connection 98.180.124.103:21054 lastseen=8.9hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.6hrs connection timeout trying connection 73.79.240.65:21054 lastseen=8.9hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.6hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.6hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.6hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.6hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.6hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.6hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.6hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.6hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.6hrs connection timeout trying connection 117.5.82.35:21054 lastseen=8.9hrs connection timeout trying connection 178.89.201.232:21054 lastseen=1.1hrs connection timeout trying connection 93.208.84.236:21054 lastseen=6.2hrs connection timeout trying connection 65.35.19.226:21054 lastseen=3.1hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.6hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.6hrs connection timeout trying connection 88.23.78.16:21054 lastseen=8.9hrs connection timeout trying connection 178.89.201.232:21054 lastseen=1.1hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.6hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.6hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.6hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.6hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.6hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.6hrs connection timeout trying connection 178.89.201.232:21054 lastseen=1.2hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.6hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.6hrs connection timeout trying connection 178.89.201.232:21054 lastseen=1.2hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.6hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.6hrs connection timeout trying connection 96.252.68.190:21054 lastseen=9.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.6hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.6hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.6hrs connection timeout trying connection 173.239.232.58:21054 lastseen=9.0hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.7hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.6hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.6hrs connection timeout trying connection 93.208.84.236:21054 lastseen=6.2hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.7hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.7hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.7hrs connection timeout trying connection 65.35.19.226:21054 lastseen=3.1hrs connection timeout trying connection 178.89.201.232:21054 lastseen=1.2hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.7hrs connection timeout trying connection 65.35.19.226:21054 lastseen=3.1hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.7hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.7hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.7hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.7hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.7hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.7hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.7hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.7hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.7hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.7hrs connection timeout trying connection 79.246.227.179:21054 lastseen=12.0hrs connection timeout trying connection 73.79.240.65:21054 lastseen=9.0hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.7hrs connection timeout trying connection 188.162.200.191:21054 lastseen=106.1hrs connection timeout trying connection 178.89.201.232:21054 lastseen=1.2hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.7hrs connection timeout trying connection 14.163.119.75:21054 lastseen=1.6hrs connection timeout trying connection 138.197.199.5:21054 lastseen=9.0hrs connection timeout trying connection 79.246.227.179:21054 lastseen=12.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.7hrs connection timeout trying connection 42.112.88.241:21054 lastseen=5.7hrs Flushed 67 addresses to peers.dat 128ms connection timeout trying connection 96.58.82.226:21054 lastseen=12.0hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.7hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.7hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.7hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.7hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.7hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.7hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.7hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.7hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.7hrs connection timeout trying connection 178.89.201.232:21054 lastseen=1.2hrs connection timeout trying connection 79.168.193.22:21054 lastseen=11.7hrs connection timeout trying connection 79.246.227.179:21054 lastseen=12.0hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.7hrs connection timeout trying connection 108.4.210.169:21054 lastseen=1.1hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.7hrs connection timeout trying connection 173.208.164.34:21054 lastseen=19.7hrs connection timeout
if you're using wallet v2.0.0.1, i'd just let it run for a while, it should hook up. if not, then retry the dl you can also look at the .log file, the last few hundred lines will do their own explaining [help]>[information tab]>[open] debug log file the user/pass thing is optional unless you plan to solo mine, or otherwise use RPC, in which case you should create your own unique and difficult to guess inputs Oh! maybe you made a common mistake: I copy and pasted this into the hempcoin.conf txt file that is in the root directory of the Hempcoin appdata folder pls check and make sure the conf file is named hempcoin.conf, not hempcoin.conf.txt, which may be the result if you're not careful in windows be sure to restart the wallet after making any changes to the .conf
|
|
|
|
groggin
Legendary
Offline
Activity: 1894
Merit: 1001
|
|
August 24, 2017, 07:36:36 PM Last edit: August 24, 2017, 07:47:36 PM by groggin |
|
Just noticed I'm on wallet v.2.0.0.0 [is that maybe the problem?]
yeah, might be, but it seems that NO ONE EVER UPDATED THE OP with a link to the latest version. i searched the thread, and someone had been reposting a link to griffith's website, but those are not working. i'll see if i have a copy to put somewhere [edit] so here you go, hempcoin v2.0.0.1 https://drive.google.com/open?id=0B-EIEoh8FDQ0YnRsWjcwMFY0UkE
|
|
|
|
|