zecon
Full Member
Offline
Activity: 364
Merit: 100
spattered throughout the golden ethers
|
|
August 28, 2017, 05:28:51 AM |
|
damn guys 800%
Just $10,000 in 24hour volume
Hmm
MASTERNODES MAX LEE HODLERS TORNADOS FLAMETHROWERS
|
If you really want to do something, you’ll find a way. If you don’t, you’ll find an excuse. — Jim Rohn
|
|
|
|
kikhtr
|
|
August 28, 2017, 06:18:29 AM |
|
Hodlcoin pump but all my coins locked. Wait for next pump
|
|
|
|
spmjnkbx
Newbie
Offline
Activity: 23
Merit: 0
|
|
August 28, 2017, 01:51:55 PM |
|
Yeah I totally bought some at 19 a couple days ago and sold at 190 last night. That was fun!
|
|
|
|
Fishmaster42
|
|
August 29, 2017, 12:42:57 AM |
|
Lets build and new wallet with a master node and our locking interest system. It's about that time again. Freetrade are you working?
|
|
|
|
kaltun
|
|
August 29, 2017, 12:14:04 PM |
|
Lets build and new wallet with a master node and our locking interest system. It's about that time again. Freetrade are you working?
very nice idea, i like it , i am in with masternode
|
|
|
|
DisasterFaster
|
|
August 29, 2017, 05:23:39 PM |
|
Noticed a bit of chatter in here about the dev FreeTrade dropping HoDl coin. I don't see that happening or at least I don't think it's very likely. He has too much time and energy in this coin to just walk away. He also holds a substantial amount of coins and so it's in his best interest to see the coin grow and value. I think a more reasonable explanation is that he is busy working on other things and in time he'll work his way back around to HoDl. One last thing, I follow this coin at Github and fairly recently a good deal of coding work has been going on for HoDl coin. Here again it wouldn't seem logical to me that a substantial investment of time reworking code would be in play if someone was planning to just walk away from the project.
Lastly and worst worst case scenario the coin still won't die. It has a good and dedicated community so myself or someone else would most definitely pick up and take over and keep moving...
Long live HoDl!
|
|
|
|
Fishmaster42
|
|
August 29, 2017, 06:01:55 PM |
|
Noticed a bit of chatter in here about the dev FreeTrade dropping HoDl coin. I don't see that happening or at least I don't think it's very likely. He has too much time and energy in this coin to just walk away. He also holds a substantial amount of coins and so it's in his best interest to see the coin grow and value. I think a more reasonable explanation is that he is busy working on other things and in time he'll work his way back around to HoDl. One last thing, I follow this coin at Github and fairly recently a good deal of coding work has been going on for HoDl coin. Here again it wouldn't seem logical to me that a substantial investment of time reworking code would be in play if someone was planning to just walk away from the project.
Lastly and worst worst case scenario the coin still won't die. It has a good and dedicated community so myself or someone else would most definitely pick up and take over and keep moving...
Long live HoDl!
Nice post, I havent stalked his gethub you reminding me of my job. Glad to hear hes in his underground lair coding away.
|
|
|
|
ghobson
Full Member
Offline
Activity: 250
Merit: 100
Crypto Developer
|
|
August 29, 2017, 08:27:00 PM |
|
Noticed a bit of chatter in here about the dev FreeTrade dropping HoDl coin. I don't see that happening or at least I don't think it's very likely. He has too much time and energy in this coin to just walk away. He also holds a substantial amount of coins and so it's in his best interest to see the coin grow and value. I think a more reasonable explanation is that he is busy working on other things and in time he'll work his way back around to HoDl. One last thing, I follow this coin at Github and fairly recently a good deal of coding work has been going on for HoDl coin. Here again it wouldn't seem logical to me that a substantial investment of time reworking code would be in play if someone was planning to just walk away from the project.
Lastly and worst worst case scenario the coin still won't die. It has a good and dedicated community so myself or someone else would most definitely pick up and take over and keep moving...
Long live HoDl!
Lets not forget its summer holliday in most of the world except usa
|
Join the boid community, earn crypto while doing real research with your cpu/gpu boid.com
|
|
|
bjew49
Newbie
Offline
Activity: 2
Merit: 0
|
|
August 30, 2017, 01:10:24 PM Last edit: August 31, 2017, 09:24:46 PM by bjew49 |
|
Hallo, ich bekomme kurz nach dem Start von Hodlcoin-qt (v3.0.1) folgende Fehlermeldung: "Fehler beim Öffnen der Blockdatenbank" "Möchten Sie die Blockdatenbank neu aufbauen?" " >Ja< >Nein<" Bei beiden Antworten wird Hodlcoin beendet. Was muss ich machen, um wieder starten zu können? Danke Bernhard ------------------ jetzt neuer Fehler: Assertion failed! Program: <pfad>\hodlcoin-qt.exe File: main.cpp, Line 1845 Expression: hashPrevBlock == view.GetBestBlock() <Abbrechen> <Wiederholen> <ignorieren> habe es mal mit "ignorieren" versucht Dann wird die Oberfläche (Wallet) angezeigt mit 0.00 HODL aber synchronisiert mit Netzwerk 1 Jahr, 30 Wochen Rückstand. mal sehen ---------------- So, hat sich erledigt, Daten neu aufgesetzt Dir: blocks und chainstate gelöscht, neu gestartet und synchronisiert. Alles wieder da 31.8.17
|
|
|
|
phunixx
Member
Offline
Activity: 121
Merit: 10
|
|
August 30, 2017, 02:57:32 PM |
|
It says 0 active connections to HODLcoin network........ Any help?
|
|
|
|
Deborah
|
|
August 30, 2017, 03:03:22 PM |
|
This will not make it a hoax.It's just not a very good idea.Developer dumping?If he was a hoax.Yes, it was almost forced.It's just a waste of time, if you ask me.But people have to learn.I'm glad I don't have too much waste of my time.
|
|
|
|
FoxyBit
Newbie
Offline
Activity: 16
Merit: 0
|
|
August 30, 2017, 07:53:04 PM |
|
Hi all,
I updated hodlcoin wallet to 3.0.1 two days ago and now I'm stuck with the message "No block source available". Anyone able to help kick this back into action? I'm not sure if there's any information that'll be needed, but just ask if there is.
TIA
You have to add the nodes. See a couple pages back. I don't think wallets have to be downloadable without updated nodes if it's gone on too long. Maybe the dev can upload a new one. I tried using this method which I found on page 213: It shouldn't be necessary but here is one option: Go to http://www.fuzzbawls.pw/explore/HOdlcoin/network.phpNow scroll down on the left side and find /HOdlcoin:3.0.0/ and then click the Nodes button A window will pop up listing a bunch of node IP addresses and you can record them Now go to your HOdl coin wallet At the top click on Help and then click on Debug Window You get a new popup and click on the Console tab When the Console opens enter the command shown below: addnode 1.124.48.250 add Repeat the process to add additional nodes as desired Good Luck! But I get the message: Method not found (code -32601) EDIT: I used the /HOdlcoin:3.0.1/ as I'm using that version. copy paste this command addnode 186.233.152.221 add you are typing in wrong way Still not getting this to update. I have added lots of nodes, but still nothing. In the error log I get: 2017-08-30 12:06:56 ProcessMessages(version, 105 bytes) FAILED peer=6 2017-08-30 12:12:22 ERROR: AcceptBlockHeader: block is marked invalid 2017-08-30 12:12:22 ERROR: invalid header received 2017-08-30 12:12:22 ProcessMessages(headers, 178003 bytes) FAILED peer=4 2017-08-30 12:13:27 receive version message: /HOdlcoin:3.0.0.99/: version 250000, blocks=307294, us=90.255.91.121:2077, peer=7 2017-08-30 12:13:27 Added time data, samples 7, offset +1 (+0 minutes) 2017-08-30 12:13:27 nTimeOffset = +0 (+0 minutes) 2017-08-30 12:15:03 receive version message: /HOdlcoin:3.0.0.99/: version 250000, blocks=307294, us=90.255.91.121:2135, peer=8 2017-08-30 12:15:03 Added time data, samples 8, offset +0 (+0 minutes) 2017-08-30 12:40:01 peer=9 using obsolete version 70010; disconnecting 2017-08-30 12:40:01 ProcessMessages(version, 102 bytes) FAILED peer=9 2017-08-30 12:40:01 socket send error An operation was attempted on something that is not a socket. (10038) 2017-08-30 13:06:33 peer=10 using obsolete version 70010; disconnecting 2017-08-30 13:06:33 ProcessMessages(version, 102 bytes) FAILED peer=10 2017-08-30 13:06:33 socket send error An operation was attempted on something that is not a socket. (10038) 2017-08-30 13:15:28 peer=11 using obsolete version 70010; disconnecting 2017-08-30 13:15:28 ProcessMessages(version, 105 bytes) FAILED peer=11 2017-08-30 13:15:28 socket send error An operation was attempted on something that is not a socket. (10038) 2017-08-30 13:28:58 peer=12 using obsolete version 70010; disconnecting 2017-08-30 13:28:58 ProcessMessages(version, 102 bytes) FAILED peer=12 2017-08-30 13:28:58 socket send error An operation was attempted on something that is not a socket. (10038) 2017-08-30 13:43:47 peer=13 using obsolete version 70010; disconnecting 2017-08-30 13:43:47 ProcessMessages(version, 102 bytes) FAILED peer=13 2017-08-30 13:44:16 peer=14 using obsolete version 70010; disconnecting 2017-08-30 13:44:16 ProcessMessages(version, 105 bytes) FAILED peer=14 2017-08-30 14:29:36 peer=15 using obsolete version 70010; disconnecting 2017-08-30 14:29:36 ProcessMessages(version, 102 bytes) FAILED peer=15 2017-08-30 14:42:04 peer=16 using obsolete version 70010; disconnecting 2017-08-30 14:42:04 ProcessMessages(version, 102 bytes) FAILED peer=16 2017-08-30 15:01:04 peer=17 using obsolete version 70010; disconnecting 2017-08-30 15:01:04 ProcessMessages(version, 105 bytes) FAILED peer=17 2017-08-30 15:08:54 peer=18 using obsolete version 70010; disconnecting 2017-08-30 15:08:54 ProcessMessages(version, 102 bytes) FAILED peer=18 2017-08-30 15:31:13 peer=19 using obsolete version 70010; disconnecting 2017-08-30 15:31:13 ProcessMessages(version, 105 bytes) FAILED peer=19 2017-08-30 15:31:13 socket send error An operation was attempted on something that is not a socket. (10038) 2017-08-30 16:16:14 peer=20 using obsolete version 70010; disconnecting 2017-08-30 16:16:14 ProcessMessages(version, 102 bytes) FAILED peer=20 2017-08-30 16:35:33 socket recv error An existing connection was forcibly closed by the remote host. (10054) 2017-08-30 16:41:18 peer=22 using obsolete version 70010; disconnecting 2017-08-30 16:41:18 ProcessMessages(version, 102 bytes) FAILED peer=22 2017-08-30 16:52:26 peer=23 using obsolete version 70010; disconnecting 2017-08-30 16:52:26 ProcessMessages(version, 102 bytes) FAILED peer=23 2017-08-30 17:18:25 peer=24 using obsolete version 70010; disconnecting 2017-08-30 17:18:25 ProcessMessages(version, 102 bytes) FAILED peer=24 2017-08-30 17:24:21 peer=25 using obsolete version 70010; disconnecting 2017-08-30 17:24:21 ProcessMessages(version, 105 bytes) FAILED peer=25 2017-08-30 17:24:21 socket send error An operation was attempted on something that is not a socket. (10038) 2017-08-30 17:40:48 peer=26 using obsolete version 70010; disconnecting 2017-08-30 17:40:48 ProcessMessages(version, 102 bytes) FAILED peer=26 2017-08-30 17:51:27 peer=27 using obsolete version 70010; disconnecting 2017-08-30 17:51:27 ProcessMessages(version, 102 bytes) FAILED peer=27 2017-08-30 18:13:07 peer=28 using obsolete version 70010; disconnecting 2017-08-30 18:13:07 ProcessMessages(version, 102 bytes) FAILED peer=28 2017-08-30 18:13:07 socket send error An operation was attempted on something that is not a socket. (10038) 2017-08-30 18:16:23 peer=29 using obsolete version 70010; disconnecting 2017-08-30 18:16:23 ProcessMessages(version, 102 bytes) FAILED peer=29 2017-08-30 18:25:13 socket recv error An existing connection was forcibly closed by the remote host. (10054) 2017-08-30 18:26:46 peer=31 using obsolete version 70010; disconnecting 2017-08-30 18:26:46 ProcessMessages(version, 102 bytes) FAILED peer=31 2017-08-30 18:26:46 socket send error An operation was attempted on something that is not a socket. (10038) 2017-08-30 18:34:21 peer=32 using obsolete version 70010; disconnecting 2017-08-30 18:34:21 ProcessMessages(version, 105 bytes) FAILED peer=32 2017-08-30 18:39:18 peer=33 using obsolete version 70010; disconnecting 2017-08-30 18:39:18 ProcessMessages(version, 102 bytes) FAILED peer=33 2017-08-30 18:39:18 socket send error An operation was attempted on something that is not a socket. (10038) And then this just repeats all the way through, just with different peer numbers. Now two weeks behind.
|
|
|
|
DenisZabar
|
|
August 30, 2017, 10:46:24 PM |
|
Hi all,
I updated hodlcoin wallet to 3.0.1 two days ago and now I'm stuck with the message "No block source available". Anyone able to help kick this back into action? I'm not sure if there's any information that'll be needed, but just ask if there is.
TIA
You have to add the nodes. See a couple pages back. I don't think wallets have to be downloadable without updated nodes if it's gone on too long. Maybe the dev can upload a new one. I tried using this method which I found on page 213: It shouldn't be necessary but here is one option: Go to http://www.fuzzbawls.pw/explore/HOdlcoin/network.phpNow scroll down on the left side and find /HOdlcoin:3.0.0/ and then click the Nodes button A window will pop up listing a bunch of node IP addresses and you can record them Now go to your HOdl coin wallet At the top click on Help and then click on Debug Window You get a new popup and click on the Console tab When the Console opens enter the command shown below: addnode 1.124.48.250 add Repeat the process to add additional nodes as desired Good Luck! But I get the message: Method not found (code -32601) EDIT: I used the /HOdlcoin:3.0.1/ as I'm using that version. copy paste this command addnode 186.233.152.221 add you are typing in wrong way Still not getting this to update. I have added lots of nodes, but still nothing. In the error log I get: 2017-08-30 12:06:56 ProcessMessages(version, 105 bytes) FAILED peer=6 2017-08-30 12:12:22 ERROR: AcceptBlockHeader: block is marked invalid 2017-08-30 12:12:22 ERROR: invalid header received 2017-08-30 12:12:22 ProcessMessages(headers, 178003 bytes) FAILED peer=4 2017-08-30 12:13:27 receive version message: /HOdlcoin:3.0.0.99/: version 250000, blocks=307294, us=90.255.91.121:2077, peer=7 2017-08-30 12:13:27 Added time data, samples 7, offset +1 (+0 minutes) 2017-08-30 12:13:27 nTimeOffset = +0 (+0 minutes) 2017-08-30 12:15:03 receive version message: /HOdlcoin:3.0.0.99/: version 250000, blocks=307294, us=90.255.91.121:2135, peer=8 2017-08-30 12:15:03 Added time data, samples 8, offset +0 (+0 minutes) 2017-08-30 12:40:01 peer=9 using obsolete version 70010; disconnecting 2017-08-30 12:40:01 ProcessMessages(version, 102 bytes) FAILED peer=9 2017-08-30 12:40:01 socket send error An operation was attempted on something that is not a socket. (10038) 2017-08-30 13:06:33 peer=10 using obsolete version 70010; disconnecting 2017-08-30 13:06:33 ProcessMessages(version, 102 bytes) FAILED peer=10 2017-08-30 13:06:33 socket send error An operation was attempted on something that is not a socket. (10038) 2017-08-30 13:15:28 peer=11 using obsolete version 70010; disconnecting 2017-08-30 13:15:28 ProcessMessages(version, 105 bytes) FAILED peer=11 2017-08-30 13:15:28 socket send error An operation was attempted on something that is not a socket. (10038) 2017-08-30 13:28:58 peer=12 using obsolete version 70010; disconnecting 2017-08-30 13:28:58 ProcessMessages(version, 102 bytes) FAILED peer=12 2017-08-30 13:28:58 socket send error An operation was attempted on something that is not a socket. (10038) 2017-08-30 13:43:47 peer=13 using obsolete version 70010; disconnecting 2017-08-30 13:43:47 ProcessMessages(version, 102 bytes) FAILED peer=13 2017-08-30 13:44:16 peer=14 using obsolete version 70010; disconnecting 2017-08-30 13:44:16 ProcessMessages(version, 105 bytes) FAILED peer=14 2017-08-30 14:29:36 peer=15 using obsolete version 70010; disconnecting 2017-08-30 14:29:36 ProcessMessages(version, 102 bytes) FAILED peer=15 2017-08-30 14:42:04 peer=16 using obsolete version 70010; disconnecting 2017-08-30 14:42:04 ProcessMessages(version, 102 bytes) FAILED peer=16 2017-08-30 15:01:04 peer=17 using obsolete version 70010; disconnecting 2017-08-30 15:01:04 ProcessMessages(version, 105 bytes) FAILED peer=17 2017-08-30 15:08:54 peer=18 using obsolete version 70010; disconnecting 2017-08-30 15:08:54 ProcessMessages(version, 102 bytes) FAILED peer=18 2017-08-30 15:31:13 peer=19 using obsolete version 70010; disconnecting 2017-08-30 15:31:13 ProcessMessages(version, 105 bytes) FAILED peer=19 2017-08-30 15:31:13 socket send error An operation was attempted on something that is not a socket. (10038) 2017-08-30 16:16:14 peer=20 using obsolete version 70010; disconnecting 2017-08-30 16:16:14 ProcessMessages(version, 102 bytes) FAILED peer=20 2017-08-30 16:35:33 socket recv error An existing connection was forcibly closed by the remote host. (10054) 2017-08-30 16:41:18 peer=22 using obsolete version 70010; disconnecting 2017-08-30 16:41:18 ProcessMessages(version, 102 bytes) FAILED peer=22 2017-08-30 16:52:26 peer=23 using obsolete version 70010; disconnecting 2017-08-30 16:52:26 ProcessMessages(version, 102 bytes) FAILED peer=23 2017-08-30 17:18:25 peer=24 using obsolete version 70010; disconnecting 2017-08-30 17:18:25 ProcessMessages(version, 102 bytes) FAILED peer=24 2017-08-30 17:24:21 peer=25 using obsolete version 70010; disconnecting 2017-08-30 17:24:21 ProcessMessages(version, 105 bytes) FAILED peer=25 2017-08-30 17:24:21 socket send error An operation was attempted on something that is not a socket. (10038) 2017-08-30 17:40:48 peer=26 using obsolete version 70010; disconnecting 2017-08-30 17:40:48 ProcessMessages(version, 102 bytes) FAILED peer=26 2017-08-30 17:51:27 peer=27 using obsolete version 70010; disconnecting 2017-08-30 17:51:27 ProcessMessages(version, 102 bytes) FAILED peer=27 2017-08-30 18:13:07 peer=28 using obsolete version 70010; disconnecting 2017-08-30 18:13:07 ProcessMessages(version, 102 bytes) FAILED peer=28 2017-08-30 18:13:07 socket send error An operation was attempted on something that is not a socket. (10038) 2017-08-30 18:16:23 peer=29 using obsolete version 70010; disconnecting 2017-08-30 18:16:23 ProcessMessages(version, 102 bytes) FAILED peer=29 2017-08-30 18:25:13 socket recv error An existing connection was forcibly closed by the remote host. (10054) 2017-08-30 18:26:46 peer=31 using obsolete version 70010; disconnecting 2017-08-30 18:26:46 ProcessMessages(version, 102 bytes) FAILED peer=31 2017-08-30 18:26:46 socket send error An operation was attempted on something that is not a socket. (10038) 2017-08-30 18:34:21 peer=32 using obsolete version 70010; disconnecting 2017-08-30 18:34:21 ProcessMessages(version, 105 bytes) FAILED peer=32 2017-08-30 18:39:18 peer=33 using obsolete version 70010; disconnecting 2017-08-30 18:39:18 ProcessMessages(version, 102 bytes) FAILED peer=33 2017-08-30 18:39:18 socket send error An operation was attempted on something that is not a socket. (10038) And then this just repeats all the way through, just with different peer numbers. Now two weeks behind. Are you behind firewall? Did you try on another computer or a laptop to get update? insert command getnetworkinfo and paste here also are you sure using version 3.0.1? this log shows 3.0.99
|
|
|
|
phunixx
Member
Offline
Activity: 121
Merit: 10
|
|
August 30, 2017, 11:15:29 PM |
|
Still no succes here adding nodes and connecting... Am behind 24 weeks and cant find any connections.
|
|
|
|
FoxyBit
Newbie
Offline
Activity: 16
Merit: 0
|
|
August 31, 2017, 01:54:50 PM |
|
Hi all,
I updated hodlcoin wallet to 3.0.1 two days ago and now I'm stuck with the message "No block source available". Anyone able to help kick this back into action? I'm not sure if there's any information that'll be needed, but just ask if there is.
TIA
You have to add the nodes. See a couple pages back. I don't think wallets have to be downloadable without updated nodes if it's gone on too long. Maybe the dev can upload a new one. I tried using this method which I found on page 213: It shouldn't be necessary but here is one option: Go to http://www.fuzzbawls.pw/explore/HOdlcoin/network.phpNow scroll down on the left side and find /HOdlcoin:3.0.0/ and then click the Nodes button A window will pop up listing a bunch of node IP addresses and you can record them Now go to your HOdl coin wallet At the top click on Help and then click on Debug Window You get a new popup and click on the Console tab When the Console opens enter the command shown below: addnode 1.124.48.250 add Repeat the process to add additional nodes as desired Good Luck! But I get the message: Method not found (code -32601) EDIT: I used the /HOdlcoin:3.0.1/ as I'm using that version. copy paste this command addnode 186.233.152.221 add you are typing in wrong way Still not getting this to update. I have added lots of nodes, but still nothing. In the error log I get: 2017-08-30 12:06:56 ProcessMessages(version, 105 bytes) FAILED peer=6 2017-08-30 12:12:22 ERROR: AcceptBlockHeader: block is marked invalid 2017-08-30 12:12:22 ERROR: invalid header received 2017-08-30 12:12:22 ProcessMessages(headers, 178003 bytes) FAILED peer=4 2017-08-30 12:13:27 receive version message: /HOdlcoin:3.0.0.99/: version 250000, blocks=307294, us=90.255.91.121:2077, peer=7 2017-08-30 12:13:27 Added time data, samples 7, offset +1 (+0 minutes) 2017-08-30 12:13:27 nTimeOffset = +0 (+0 minutes) 2017-08-30 12:15:03 receive version message: /HOdlcoin:3.0.0.99/: version 250000, blocks=307294, us=90.255.91.121:2135, peer=8 2017-08-30 12:15:03 Added time data, samples 8, offset +0 (+0 minutes) 2017-08-30 12:40:01 peer=9 using obsolete version 70010; disconnecting 2017-08-30 12:40:01 ProcessMessages(version, 102 bytes) FAILED peer=9 2017-08-30 12:40:01 socket send error An operation was attempted on something that is not a socket. (10038) 2017-08-30 13:06:33 peer=10 using obsolete version 70010; disconnecting 2017-08-30 13:06:33 ProcessMessages(version, 102 bytes) FAILED peer=10 2017-08-30 13:06:33 socket send error An operation was attempted on something that is not a socket. (10038) 2017-08-30 13:15:28 peer=11 using obsolete version 70010; disconnecting 2017-08-30 13:15:28 ProcessMessages(version, 105 bytes) FAILED peer=11 2017-08-30 13:15:28 socket send error An operation was attempted on something that is not a socket. (10038) 2017-08-30 13:28:58 peer=12 using obsolete version 70010; disconnecting 2017-08-30 13:28:58 ProcessMessages(version, 102 bytes) FAILED peer=12 2017-08-30 13:28:58 socket send error An operation was attempted on something that is not a socket. (10038) 2017-08-30 13:43:47 peer=13 using obsolete version 70010; disconnecting 2017-08-30 13:43:47 ProcessMessages(version, 102 bytes) FAILED peer=13 2017-08-30 13:44:16 peer=14 using obsolete version 70010; disconnecting 2017-08-30 13:44:16 ProcessMessages(version, 105 bytes) FAILED peer=14 2017-08-30 14:29:36 peer=15 using obsolete version 70010; disconnecting 2017-08-30 14:29:36 ProcessMessages(version, 102 bytes) FAILED peer=15 2017-08-30 14:42:04 peer=16 using obsolete version 70010; disconnecting 2017-08-30 14:42:04 ProcessMessages(version, 102 bytes) FAILED peer=16 2017-08-30 15:01:04 peer=17 using obsolete version 70010; disconnecting 2017-08-30 15:01:04 ProcessMessages(version, 105 bytes) FAILED peer=17 2017-08-30 15:08:54 peer=18 using obsolete version 70010; disconnecting 2017-08-30 15:08:54 ProcessMessages(version, 102 bytes) FAILED peer=18 2017-08-30 15:31:13 peer=19 using obsolete version 70010; disconnecting 2017-08-30 15:31:13 ProcessMessages(version, 105 bytes) FAILED peer=19 2017-08-30 15:31:13 socket send error An operation was attempted on something that is not a socket. (10038) 2017-08-30 16:16:14 peer=20 using obsolete version 70010; disconnecting 2017-08-30 16:16:14 ProcessMessages(version, 102 bytes) FAILED peer=20 2017-08-30 16:35:33 socket recv error An existing connection was forcibly closed by the remote host. (10054) 2017-08-30 16:41:18 peer=22 using obsolete version 70010; disconnecting 2017-08-30 16:41:18 ProcessMessages(version, 102 bytes) FAILED peer=22 2017-08-30 16:52:26 peer=23 using obsolete version 70010; disconnecting 2017-08-30 16:52:26 ProcessMessages(version, 102 bytes) FAILED peer=23 2017-08-30 17:18:25 peer=24 using obsolete version 70010; disconnecting 2017-08-30 17:18:25 ProcessMessages(version, 102 bytes) FAILED peer=24 2017-08-30 17:24:21 peer=25 using obsolete version 70010; disconnecting 2017-08-30 17:24:21 ProcessMessages(version, 105 bytes) FAILED peer=25 2017-08-30 17:24:21 socket send error An operation was attempted on something that is not a socket. (10038) 2017-08-30 17:40:48 peer=26 using obsolete version 70010; disconnecting 2017-08-30 17:40:48 ProcessMessages(version, 102 bytes) FAILED peer=26 2017-08-30 17:51:27 peer=27 using obsolete version 70010; disconnecting 2017-08-30 17:51:27 ProcessMessages(version, 102 bytes) FAILED peer=27 2017-08-30 18:13:07 peer=28 using obsolete version 70010; disconnecting 2017-08-30 18:13:07 ProcessMessages(version, 102 bytes) FAILED peer=28 2017-08-30 18:13:07 socket send error An operation was attempted on something that is not a socket. (10038) 2017-08-30 18:16:23 peer=29 using obsolete version 70010; disconnecting 2017-08-30 18:16:23 ProcessMessages(version, 102 bytes) FAILED peer=29 2017-08-30 18:25:13 socket recv error An existing connection was forcibly closed by the remote host. (10054) 2017-08-30 18:26:46 peer=31 using obsolete version 70010; disconnecting 2017-08-30 18:26:46 ProcessMessages(version, 102 bytes) FAILED peer=31 2017-08-30 18:26:46 socket send error An operation was attempted on something that is not a socket. (10038) 2017-08-30 18:34:21 peer=32 using obsolete version 70010; disconnecting 2017-08-30 18:34:21 ProcessMessages(version, 105 bytes) FAILED peer=32 2017-08-30 18:39:18 peer=33 using obsolete version 70010; disconnecting 2017-08-30 18:39:18 ProcessMessages(version, 102 bytes) FAILED peer=33 2017-08-30 18:39:18 socket send error An operation was attempted on something that is not a socket. (10038) And then this just repeats all the way through, just with different peer numbers. Now two weeks behind. Are you behind firewall? Did you try on another computer or a laptop to get update? insert command getnetworkinfo and paste here also are you sure using version 3.0.1? this log shows 3.0.99 In the About HOdlcoin Core, it definitely says Version 3.0.1. Here's the result of 'getnetworkinfo': { "version" : 3000100, "subversion" : "/HOdlcoin:3.0.1/", "protocolversion" : 250000, "localservices" : "0000000000000001", "timeoffset" : 1, "connections" : 8, "networks" : [ { "name" : "ipv4", "limited" : false, "reachable" : false, "proxy" : "", "proxy_randomize_credentials" : false }, { "name" : "ipv6", "limited" : false, "reachable" : false, "proxy" : "", "proxy_randomize_credentials" : false }, { "name" : "onion", "limited" : false, "reachable" : false, "proxy" : "", "proxy_randomize_credentials" : false } ], "relayfee" : 0.00005000, "localaddresses" : [ ] }
|
|
|
|
trade718
Newbie
Offline
Activity: 4
Merit: 0
|
|
September 01, 2017, 07:34:18 AM |
|
https://i.imgur.com/C4hswXe.pngI'm new to this coin and my rig has been running for 5 hours but I don't see any coin mined. Did I miss something?
|
|
|
|
DenisZabar
|
|
September 01, 2017, 10:05:30 AM |
|
I'm new to this coin and my rig has been running for 5 hours but I don't see any coin mined. Did I miss something? You are mining @114h/ps When you calculate that http://samuelpj.github.io/hodl-mining-calc/? you get one block per 24hours. So everything is fine you need to wait...
|
|
|
|
DenisZabar
|
|
September 01, 2017, 07:10:31 PM |
|
Still no succes here adding nodes and connecting... Am behind 24 weeks and cant find any connections.
Did you try to download blockchain on any other computer outside of your home?
|
|
|
|
phunixx
Member
Offline
Activity: 121
Merit: 10
|
|
September 02, 2017, 08:32:39 PM Last edit: September 02, 2017, 08:58:27 PM by phunixx |
|
Still no succes here adding nodes and connecting... Am behind 24 weeks and cant find any connections.
Did you try to download blockchain on any other computer outside of your home? Sorted it out......thx
|
|
|
|
|