Bitcoin Forum
June 24, 2024, 09:56:32 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 [2] 3 4 5 6 7 8 9 »
21  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] Sia - Decentralized Storage on: September 03, 2017, 05:41:23 PM
Quote from: Hakkane on September 03, 2017, 03:11:26 PM
Quote from: attilafx on September 03, 2017, 08:51:34 AM
If I want to buy Sia low and cheap you could argue that I already can since it is trading below 1000 sats. look at the market orders. right now there are 40 BTC buyers and 10 BTC sellers in the range of 180 to 190. Still price is grinding lower. There is no buying interest in SIA. and with a zillion BTC traded on a single day you can not deny that the market isn't interested in this coin. And there I go back to my initial statement. If it was such a great coin we wouldn't trade this low at all. I'm not here to ruin the party, but you have to see the fact that the market isn't interested and if the market overall isn't interested you might actually see much much lower prices. Especially as the dumping continues because somebody is selling all the time.

There are 30 billions of Siacoin in circulation, so valuing the project at $230 millions. That is a market cap 10 times more than 4 months ago, 20 times more than 5 month ago and 200 times more than one year ago. Do you dare to say there is no interest in the project? Sia is an already functional product offering 3 petabytes of data so far among 750 hosts, but there is of course room for new features (all of them are in their roadmap https://trello.com/b/Io1dDyuI/sia-public-roadmap) and a lot of room for adoption growth: the value will keep growing naturally the closer we get to the endgame of Sia.

Your problem is also that you are using as a reference of the value of Sia the Bitcoin. That is a bad idea in general: how can you use a reference point for the value of Sia a coin that has duplicated its value during the last month? That's a horrible control. Is anybody panicking around about the dollar devaluation because the USD/BTC charts say so? But in the case of Sia it has even less sense to use the BTC as a control for its value, as file contract prices are adjusted manually to dollar prices by the hosts. It is an economy linked t dollar prices. And if you check the SC/USD charts, you'll see Sia has grown enormously, reached a peak at 2 cents on May, and since then it has been stable at the 0.7-1 cent of dollar.

Ultimately, still you are only using market charts to determine how good a project is. Seiously @attilafx, if you are an investor and you are only looking at BTC charts to know which projects are good or not instead of checking more info, digging in the communities and learning abut upcoming features, sell right now all your positions in cryptos because very soon you are going to lose everything

Extremely well said.  Fundamental Analysis / market research is almost EVERYTHING.
22  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][THC] The Hempcoin (THC) on: August 25, 2017, 12:33:09 AM
With the new wallet downloaded 2.0.0.1, I am having no issues at all.  Syncing to the blockchain right now with 10 active connections, just need to see it finish  Grin
23  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][THC] The Hempcoin (THC) on: August 24, 2017, 10:09:47 PM
Quote from: groggin on August 24, 2017, 07:36:36 PM
Quote from: CryptoKeeper802
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

Thank you, it seems the answer to my problems is likely very simple as usual.  I'll give this a try now  Smiley
24  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][THC] The Hempcoin (THC) on: 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]:

Code:

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


Quote from: groggin on August 24, 2017, 12:13:44 PM
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  Wink

[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:

Quote
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
25  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][THC] The Hempcoin (THC) on: 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?

Quote from: groggin on August 24, 2017, 06:24:46 AM
Quote
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
Code:
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
26  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][THC] The Hempcoin (THC) on: 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?

Quote from: Joint Force on August 24, 2017, 04:09:04 AM
Quote from: CryptoKeeper802 on August 23, 2017, 08:31:10 PM
I tried parsing the list and made a hempcoin.conf file that contains the following:

Code:
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.
27  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][THC] The Hempcoin (THC) on: August 24, 2017, 05:29:13 AM
Quote from: groggin on August 24, 2017, 04:43:06 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.
28  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][THC] The Hempcoin (THC) on: August 23, 2017, 08:31:10 PM
I tried parsing the list and made a hempcoin.conf file that contains the following:

Code:
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?

Quote from: groggin on August 23, 2017, 07:13:00 PM
Quote from: CryptoKeeper802 on 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?

 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
29  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][THC] The Hempcoin (THC) on: 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?

Code:
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
}
]



Quote from: groggin on August 23, 2017, 04:50:23 PM
Quote from: CryptoKeeper802 on 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?  

here's a copy of my hempcoin.conf:
Code:
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  Wink


Code:
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
}
]
30  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][THC] The Hempcoin (THC) on: 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? 
31  Alternate cryptocurrencies / Announcements (Altcoins) / Re: ★★DigiByte|极特币★★[DGB]✔ DigiSync v6.14.2 - DigiSpeed - Segwit -DiguSign on: July 01, 2017, 08:27:06 PM
Yep this coin is getting squeezed like other good coins in past cycles have been squeezed.  Syscoin being an example when it was squeezed to it's low of 600's last year.  Let the pain continue I guess.
32  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN]🔥DOPECOIN🔥2nd ONLINE SHOP UP AND RUNNING - ARMY OF SHOPS TO FOLLOW🔥 on: May 19, 2017, 05:18:13 AM
Dopecoin is a good name for this coin, it would be stupid to re-brand it.  Go home with that suggestion, and may the Dopest coin march on!
33  Economy / Web Wallets / Re: Blockchain.info - Bitcoin Block explorer & Currency Statistics on: May 16, 2017, 09:42:37 PM
What's going on with wallet access today?  Anyone else unable to login due to the site not responding?
34  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000 on: May 16, 2017, 06:48:56 PM
This is an amazing coin doing blockchain in a really smart way that nobody else out there is doing, buy and hold!
35  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][THC][1.7] The Hempcoin (THC) ✿ UPGRADED POW/POS ✿ Spread the Seeds ✿ EPIC on: May 14, 2017, 08:29:39 AM
THC / The Hemp Coin is pumping up with nice buy support on Bittrex right now... any news?
36  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN]🏆🏆DOPECOIN🏆🏆BREAKING NEWS!! - DISPENSARY PARTNERSHIP ESTABLISHED🏆🏆 on: May 10, 2017, 06:04:42 AM
Quote from: dopey on May 01, 2017, 10:34:00 AM
Greetings team DopeCoin!

I just wanted to give everyone a quick update on what is going on with our dispensary partners.

We are currently working on starting the creation of a payment API for DopeCoin which will allow payments to be processed directly on our test shop.

Once this is completed, we will integrate the changes over to Lifted Bud and DopeCoin will soon be in place to process payments directly on the site.
In addition, we are also working on setting up DopeCoin's to be used as a reward system for frequent shoppers and those making large purchases in fiat.

Lifted Bud will also be acting on a larger scale as a wholesaler and my team and I will be personally building all-in-one shops for additional retail and local partners in Canada.

Essentially, new partners will be able to start their own shop which already comes preloaded with products, DopeCoin integration, access to medical cards and delivery and fulfillment already setup on the back end.

The new partners will simply have to adjust their prices from the wholesale pricing, (in order to make their margin) and start taking orders.

Of course, there will be some additional challenges in the process including some setup and training for everything to run smoothly.

We understand this and as a solution, we have created a test shop where this functionality will be tested and incorporated as it becomes available in order to make the process as smooth and simple for everyone involved as possible.

I will clearly state here now that I do not have anything to do with actually selling or mailing out any kinds of products but am merely setting up the technical aspects for those who are able and licensed to operate within this industry.

Now please take into consideration that this is quite ambitious and there is no guarantee that we will be successful, I am a realistic guy and I don't want to bullshit anyone. But, with that being said, it is in the pipeline and being actively worked on and things are looking pretty damn good.

Lot's of work to do!

Thank you, everyone, for your support,

Dopey



That's pretty dope!!
37  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] (XWC) | WhiteCoin | NEWS: Foundation, investors, WhiteOS ☯ whitecoin.info on: May 10, 2017, 04:45:10 AM
We don't need to do anything if our coins have just been on Bittrex?  They have already been autos-swapped?
38  Alternate cryptocurrencies / Announcements (Altcoins) / Re: DT-Token - DT Chain - Changing the World Block by Block Use Case by Use Case on: March 26, 2017, 07:01:02 AM
What's the deal with the JIO Tokens?  What exchange do they trade on?
39  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] 😍 😍 😍DOPECOIN 😍 😍 😍DEVELOPMENT BEGUN ON ANDROID WALLET 😍 MAR 15 on: March 22, 2017, 06:36:16 PM
Quote from: anotherlateminer on March 22, 2017, 07:22:51 AM
Quote from: CryptoKeeper802 on March 22, 2017, 04:43:14 AM
I uninstalled the older wallet [deleted the QT and the dopecoin app data folder] and downloaded the version 4 wallet from the website.

When I go to install the new QT file from the downloaded zip file, it gives the following error message:

The program can't start because lipwinpthread-1.dll is missing from your computer.  Try reinstalling the program to fix this program.

______

So the issue is that the dopecoin application data folder is gone, and there if I remove the new QT and try to open it from the zip file or drag a new one it still gives the same error message.
Redownload archive, please, yesterday there was a missing lib.

Just did that and it works no problem thank you!

Should I leave the QT in the same folder as it downloaded into with the lib file?  That is what I have done for now.  Waiting for it to sync, then I will try to send some coin to it.
40  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][THC][1.7] The Hempcoin (THC) ✿ UPGRADED POW/POS ✿ Spread the Seeds ✿ EPIC on: March 22, 2017, 06:27:17 PM
Quote from: casper77 on March 22, 2017, 06:34:10 AM
seems to we have a forked chain
my balance of 5 mining days disappeared and all trancactions become unconfirmed
WTF ?

Mine is still looking good.  I wonder if maybe you need to do a wallet reset.
Pages: « 1 [2] 3 4 5 6 7 8 9 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!