[ANN] Ħ [HODL] No Staking, 1% Standard Interest per Day, 750% APR For HOdlers

[FreeTrade]

@nomadicmad

I had a similar problem, my wallet client was showing 'synced' but wasn't actually at the correct block height... but deleting my blockchain data and starting from scratch worked for me. My mined coins finally appeared upon a proper sync.

I think my problem had something to do with using one of the blockchain download links from the first post. Maybe those should be updated or removed if they are indeed part of the problem.

You were correct.  the problem started when i downloaded that blockchain from the first page download link AFTER this problem occurred.  My miner and both wallets were working fine.  The problems started for me when I downloaded that shit... and attempted to fix something that was never broken on my end..so... THANKS FOR THAT.   (a sincere thank you to nomadic to actually figuring this out)

I was going to hang in there for another week or two and see how it went but ....   WAY TOO MUCH shady going on here.  Maybe you guys are legit but it doesn't appear that way from the outside. Funny how these 'issues' are never in favor of the miners.  Is there a dev team behind this or are we talking one guy part time on the weekends?

Ok, thanks - I've removed the blockchain download section temporarily given two reports of problems caused with them.

[1715206546]

1715206546

[1715206546]

1715206546

[1715206546]

1715206546

[FreeTrade]

There are a number of explanations of why mined blocks may have been orphaned.

The first is both sides of the recent fork (v2 and v3) continued to be mined and people were getting confused between the two chains. Blocks mined on v3 won't show up on v2 and vice versa. Both sides of the fork could operate independently and indefinitely, but we'd expect v2 to die out as people realise their coins aren't valid on exchanges and don't show up on the block explorer.

Another possible reason is that the recent bug which caused a number of main nodes to go down also caused a chain split, where some miners were unaffected and mined for quite some time while the major pools were down. This would have caused difficulty to go very low, and the remaining miners would have picked up a lot of blocks. The larger miners should have picked up this chain when they came back online, but it is possible the network was fractured at this point and the miners restarted from the point they left off because they were unaware of it.

Its an unfortunate situation, but it's an experimental coin and I doubt there are any nefarious explanations given the low value of the network currently. The network has now settled on the major chain. That chain contains the valid mined blocks and transactions. If your blocks and transactions are not on that chain, they are not recoverable.

[maurtis]

What do I need to do to fix this issue? Looks like both of my clients are now mining orphaned blocks. Both are v3.0.0 and were mining fine until last week, my last valid blocks according to the block explorer were on 06/06/2017.

I restarted with -zapwallettxes=1 but that does not look like it did the trick. Do I delete everything except my wallet.dat, reinstall, and run again? Or is there something else that needs to be done?

[FreeTrade]

What do I need to do to fix this issue? Looks like both of my clients are now mining orphaned blocks. Both are v3.0.0 and were mining fine until last week, my last valid blocks according to the block explorer were on 06/06/2017.

I restarted with -zapwallettxes=1 but that does not look like it did the trick. Do I delete everything except my wallet.dat, reinstall, and run again? Or is there something else that needs to be done?

Yes, that should do it - use the -zapwallettxes=1 too

[maurtis]

What do I need to do to fix this issue? Looks like both of my clients are now mining orphaned blocks. Both are v3.0.0 and were mining fine until last week, my last valid blocks according to the block explorer were on 06/06/2017.

I restarted with -zapwallettxes=1 but that does not look like it did the trick. Do I delete everything except my wallet.dat, reinstall, and run again? Or is there something else that needs to be done?

Yes, that should do it - use the -zapwallettxes=1 too

Thanks! Still waiting for one client to catch up, but that seems to have done it. The orphans are gone at least.

[wisebc]

What do I need to do to fix this issue? Looks like both of my clients are now mining orphaned blocks. Both are v3.0.0 and were mining fine until last week, my last valid blocks according to the block explorer were on 06/06/2017.

I restarted with -zapwallettxes=1 but that does not look like it did the trick. Do I delete everything except my wallet.dat, reinstall, and run again? Or is there something else that needs to be done?

Yes, that should do it - use the -zapwallettxes=1 too

Thanks! Still waiting for one client to catch up, but that seems to have done it. The orphans are gone at least.

All quiet here now, everything back to normal.

[Thepuj]

After running 2.0.0 recently I had problems syncing. So I downloaded the blockchain from the first posting and kept the wallet.dat. Same problem. Stops two days ago. So I dumped my complete blockchain and kept the wallet.dat. Still same problem. The change from good to bad is here:

2017-06-12 06:29:29 Block:CBlockIndex(pprev=0x7effcc6620c0, nHeight=263563, merkle=afe6b8242cbf55cd0d314ad700ba7dc1a203f305b5692908a03e25e7f8488eb2, hashBlock=
00000022dc8b3454c01a2f41acf30522ed5916ae747da7aaeb8d73ea3cddcbcf, nNonce=9102, nTime=1497004161, location=181639, finalcalculation=3466460353)
2017-06-12 06:29:29 UpdateTip: new best=000000196028bbe4106503223374025ed3c05b676dca913521174b2df4a3df7c  height=263564  log2_work=42.03274  tx=527478  date=20
17-06-09 10:29:55 progress=0.994632  cache=51.1MiB(236282tx)
2017-06-12 06:29:29 Block:CBlockIndex(pprev=0x7effcc6621d0, nHeight=263564, merkle=be1de94570219064b6aedb92b38c857c21ae6a5ad003d6e79bee360884c78bcc, hashBlock=
000000196028bbe4106503223374025ed3c05b676dca913521174b2df4a3df7c, nNonce=391, nTime=1497004195, location=145891, finalcalculation=270786450)
2017-06-12 06:29:29 UpdateTip: new best=000001b2a918550c53abd3dd8b5bba31d0bdbe4d
0611de6da4b056958de06b96  height=263565  log2_work=42.032743  tx=527479  date=2017-06-09 10:34:57 progress=0.994638  cache=51.1MiB(236283tx)
2017-06-12 06:29:29 Block:CBlockIndex(pprev=0x7effcc6622e0, nHeight=263565, merkle=7ff54c14374342920d52f7a94234b794170838a13f57c9d1ce21ab40c36c2072, hashBlock=000001b2a918550c53abd3dd8b5bba31d0bdbe4d0611de6da4b056958de06b96, nNonce=7958, nTime=1497004497, location=239772, finalcalculation=2902672910)
2017-06-12 06:29:29 UpdateTip: new best=000000067097c568a158f9c379b2b5a47cea881683001407a7c354f1b687d1fa  height=263566  log2_work=42.032745  tx=527480  date=2017-06-09 10:34:58 progress=0.994638  cache=51.1MiB(236284tx)
2017-06-12 06:29:29 Block:CBlockIndex(pprev=0x7effcc6623f0, nHeight=263566, merkle=9c08d4eedf8d2ceb16d71443d5724e3c1784c206019fdba4196df00f655fb588, hashBlock=000000067097c568a158f9c379b2b5a47cea881683001407a7c354f1b687d1fa, nNonce=3008, nTime=1497004498, location=178589, finalcalculation=3131149817)
2017-06-12 06:29:29 ERROR: CheckInputs(): d4858b0970b57a97e266f8d61635144dc1d7435e080e637db40a0c104f7bde90 value in (0.00242305) < value out (0.06149373)
2017-06-12 06:29:29 Misbehaving: 71.226.74.120:1989 (0 -> 100) BAN THRESHOLD EXCEEDED
2017-06-12 06:29:29 InvalidChainFound: invalid block=0000007695c99b3f795f9a6c6487a583fdc857f9db0ab6c395d41e49b3e8ae0b  height=263567  log2_work=42.032748  date=2017-06-09 10:48:41
2017-06-12 06:29:29 InvalidChainFound:  current best=000000067097c568a158f9c379b2b5a47cea881683001407a7c354f1b687d1fa  height=263566  log2_work=42.032745  date=2017-06-09 10:34:58
2017-06-12 06:29:29 ERROR: ConnectTip(): ConnectBlock 0000007695c99b3f795f9a6c6487a583fdc857f9db0ab6c395d41e49b3e8ae0b failed
2017-06-12 06:29:29 InvalidChainFound: invalid block=0000007695c99b3f795f9a6c6487a583fdc857f9db0ab6c395d41e49b3e8ae0b  height=263567  log2_work=42.032748  date=2017-06-09 10:48:41
2017-06-12 06:29:29 InvalidChainFound:  current best=000000067097c568a158f9c379b2b5a47cea881683001407a7c354f1b687d1fa  height=263566  log2_work=42.032745  date=2017-06-09 10:34:58
2017-06-12 06:29:29 receive version message: /HOdlcoin:3.0.0/: version 250000, blocks=265084, us=46.85.20.134:41361, peer=43
2017-06-12 06:29:36 receive version message: /HOdlcoin:3.0.0/: version 250000, blocks=265084, us=46.85.20.134:38682, peer=44
2017-06-12 06:31:23 ERROR: AcceptBlockHeader: block is marked invalid
2017-06-12 06:31:23 ERROR: invalid header received
2017-06-12 06:31:23 ProcessMessages(headers, 178003 bytes) FAILED peer=41
2017-06-12 06:31:24 ERROR: AcceptBlockHeader: block is marked invalid
2017-06-12 06:31:24 ERROR: invalid header received
2017-06-12 06:31:24 ProcessMessages(headers, 178003 bytes) FAILED peer=28
2017-06-12 06:31:29 ERROR: AcceptBlockHeader: block is marked invalid
2017-06-12 06:31:29 ERROR: invalid header received
2017-06-12 06:31:29 ProcessMessages(headers, 178003 bytes) FAILED peer=32
2017-06-12 06:35:54 ERROR: AcceptBlockHeader: block is marked invalid
2017-06-12 06:35:54 ERROR: invalid header received
2017-06-12 06:35:54 ProcessMessages(headers, 178003 bytes) FAILED peer=28
2017-06-12 06:35:55 ERROR: AcceptBlockHeader: block is marked invalid
2017-06-12 06:35:55 ERROR: invalid header received

I use 3.0.0 on Linux.

[Pon13]

so it wasnt only me....

i'm gonna try to make my wallet sync again....still it would be really bad to lose the coins that i've been mining for 3 days now.

[Pon13]

so it wasnt only me....

i'm gonna try to make my wallet sync again....still it would be really bad to lose the coins that i've been mining for 3 days now.

wallet synced. NO coins lost so everything is back to normal. fiiiiiiiiiiiouuuuuuuuuuu

[psyber]

on this  -zapwallettxes=1 subject  I have tryed this but keep getting   method not found  code32601 what am I doing wrong

[DisasterFaster]

on this  -zapwallettxes=1 subject  I have tryed this but keep getting   method not found  code32601 what am I doing wrong

@psyber is sounds like you are in the console and entering that command and that won't work...

If you're on windows create a shortcut icon to your wallet .exe file..

Then right click that icon and select properties...

You'll see a box called "target"

Depending on your install path it could look something like this...

D:\riecoin\riecoin-qt.exe

Now change that to something like this...

D:\riecoin\riecoin-qt.exe -zapwallettxes=1

and click apply and click okay

now click that icon and launch the wallet and it will run that command...

Now you should probably redo the above steps and remove that -zapwallettxes=1 from the target since there is no reason to do it each time you launch the wallet...

[h0g0f0g0]

Is there any future for HODL?

Price went down 1000x times, no major exchange is listing it. Trust has not been recovered IMHO. Mining is possible but nothing like it was year ago when there was community around this coin.

I believe it can move forward but we need to establish a dev team and set of services. I am willing to donate most of my hodlings to support this.

[fbastage]

restarted and resynched blockchain with seed nodes from http://www.fuzzbawls.pw/explore/HOdlcoin/network.php and STILL end up on forked chain.

how to resolve?

[autominer]

- Fresh install of HOdlcoin:3.0.0/ on ubuntu 17.04 from http://hodlcoin.com/downloads/ (https://github.com/HOdlcoin/HOdlcoin/releases/download/v3.0.0/hodlcoin-3.0.0-linux64.tar.gz)

- Ran ./hodlcoin-qt

- Client comes up fine and starts the download of the blockchain (all good so far)

- While the client is syncing it says "3 days to go" then it stops syncing

- These seems to be a block causing problems. Block number 263567 ("0000007695c99b3f795f9a6c6487a583fdc857f9db0ab6c395d41e49b3e8ae0b")

- The error is below

ERROR: CheckInputs(): d4858b0970b57a97e266f8d61635144dc1d7435e080e637db40a0c104f7bde90 value in (0.0024309) < value out (0.06149373)
2017-06-12 16:44:08 Misbehaving: 96.44.157.195:1989 (0 -> 100) BAN THRESHOLD EXCEEDED
2017-06-12 16:44:08 InvalidChainFound: invalid block=0000007695c99b3f795f9a6c6487a583fdc857f9db0ab6c395d41e49b3e8ae0b  height=263567  log2_work=42.032748  date=2017-06-09 10:48:41
2017-06-12 16:44:08 InvalidChainFound:  current best=000000067097c568a158f9c379b2b5a47cea881683001407a7c354f1b687d1fa  height=263566  log2_work=42.032745  date=2017-06-09 10:34:58
2017-06-12 16:44:08 ERROR: ConnectTip(): ConnectBlock 0000007695c99b3f795f9a6c6487a583fdc857f9db0ab6c395d41e49b3e8ae0b failed
2017-06-12 16:44:08 InvalidChainFound: invalid block=0000007695c99b3f795f9a6c6487a583fdc857f9db0ab6c395d41e49b3e8ae0b  height=263567  log2_work=42.032748  date=2017-06-09 10:48:41
2017-06-12 16:44:08 InvalidChainFound:  current best=000000067097c568a158f9c379b2b5a47cea881683001407a7c354f1b687d1fa  height=263566  log2_work=42.032745  date=2017-06-09 10:34:58


- Tried running the same process again on a fresh download. Same error.
- Tried restarting the client. No Progress
- Tried adding a number of nodes (only those that are 3.0.0) with addnode "xxxx" add from https://www.coinexchange.io/network/peers/HODL. No progress
- Tried starting the client like this ./hodlcoin-qt -addnode="88.99.30.25" -zapwallettxes=1. No Progress
- Tried all the same step on a Mac. Stops exactly at the same block 262567.

I am sorry if I have missed something here, I have gone through the forum but I still cant get the blockchain to sync completely (it stops 2/3 days short)

Thank you in advance

[bkbirge]

I had to completely wipe any hodl files except my backup wallet from my computer, *REBOOT*, then reinstall the v3.0.0 version of things and I'm good now. I did enjoy being on the wrong fork for awhile as my mining was awesome, but it was just air.  

[autominer]

I have tried this on two clean linux machines and a separate mac, each time downloading a fresh v 3.0.0 tar.gz

My blockchain has not even synched once. The QT client is still empty, no screen show can blocks / transactions from anybody.

When i start the client it tells me that I am stuck at block number 263566 whereas the chain as moved onto 265342. Later the client does connect to peers who are uptodate but does not update itself.

What should I do to get the client to sync and to look at the blockchain.


2017-06-12 19:40:20 init message: Activating best chain...
2017-06-12 19:40:20 mapBlockIndex.size() = 265342
2017-06-12 19:40:20 nBestHeight = 263566
2017-06-12 19:40:20 setKeyPool.size() = 101
2017-06-12 19:40:20 mapWallet.size() = 0
2017-06-12 19:40:20 mapAddressBook.size() = 1
2017-06-12 19:40:20 init message: Loading addresses...
2017-06-12 19:40:20 Loaded 7 addresses from peers.dat  0ms
2017-06-12 19:40:20 dnsseed thread start
2017-06-12 19:40:20 net thread start
2017-06-12 19:40:20 addcon thread start
2017-06-12 19:40:20 opencon thread start
2017-06-12 19:40:20 msghand thread start
2017-06-12 19:40:20 init message: Done loading
2017-06-12 19:40:20 GUI: PaymentServer::LoadRootCAs: Loaded  168  root certificates
2017-06-12 19:40:20 receive version message: /HOdlcoin:3.0.0/: version 250000, blocks=265366, us=103.66.14.149:51540, peer=1
2017-06-12 19:40:20 Added time data, samples 2, offset +0 (+0 minutes)
2017-06-12 19:40:21 receive version message: /HOdlcoin:3.0.0/: version 250000, blocks=265366, us=103.66.14.149:51541, peer=2
2017-06-12 19:40:21 Added time data, samples 3, offset +0 (+0 minutes)
2017-06-12 19:40:22 connect() to 217.147.160.30:1989 failed after select(): Connection refused (61)
2017-06-12 19:40:29 receive version message: /HOdlcoin:3.0.0/: version 250000, blocks=265366, us=103.66.14.149:51544, peer=3
2017-06-12 19:40:29 Added time data, samples 4, offset -11 (+0 minutes)
2017-06-12 19:40:31 P2P peers available. Skipped DNS seeding.
2017-06-12 19:40:31 dnsseed thread exit
2017-06-12 19:40:31 receive version message: /HOdlcoin:3.0.0/: version 250000, blocks=265366, us=103.66.14.149:51545, peer=4
2017-06-12 19:40:31 Added time data, samples 5, offset +1 (+0 minutes)
2017-06-12 19:40:31 nTimeOffset = +0  (+0 minutes)
2017-06-12 19:50:25 connect() to 217.147.160.30:1989 failed after select(): Connection refused (61)

[jeremyf327]

I have same problem on both of my Macs. The blockchain only syncs to 263566 and then stalls there. Seems like a bug. Anyone make progress here?

[Cannabisdreams]

If you are having problems getting your miner to sync:  DO NOT DOWNLOAD the blockchain from the link on the first page.  I have no idea why, but that file is causing problems and I can't imagine why a user supplied download link from a couple years ago has not been removed after reports of problems.  (*I see that it has been removed, thank you!
 

I had to delete every file that even looked like a hodl file except the wallet.dat (major mistake to delete that file since I haven't found a way to recover it and lost the first coins I mined).  I had to move that to my desktop, delete the entire hodlcoin folder in the appdata file and the original location you put the exe file.  That wallet fix thingy did not work no matter how many ways I tried or how angry I got at it.    The only thing that worked was deleting absolutely everything, downloading the Hodlcoin 3.0.0 zip file all over again and writing a new bat file (probably not necessary but who knows).  Lastly, put the wallet.bat file back where it belongs and launch.  

It took HOURS to download the blockchain (as expected) and during that time the cmd window showed errors and block problems...that is NORMAL, its shutting down stale/closed nodes and looking for others.. .DO NOT close the window until your wallet shows fully synced and when you put your mouse over the little icon at the bottom right, the block number matches the block the network is on (from the block explorer website).

It would be immensely helpful to have someone around to answer newcomer questions.  I'm sure there were/are plenty of new guys who didn't bother bitching on this forum and just moved on.  

[FreeTrade]

Thanks for the continued detailed bug reports.

It looks like block 263567 contains the problematic transaction with the HODL'd date in the past. For reasons I'm not yet clear on, some systems running v3.0.0 seem to accept this and others not (maybe particularly MACs?)

First thing to try, if you're compiling yourself is to use the master branch which contains a fix, and not the 3.0.0 release.
https://github.com/HOdlcoin/HOdlcoin/tree/HODLCoin0.11.3

Clearly we need a new release with this fix asap at this point. I'll finalize this shortly.

[jeremyf327]

Thanks for the continued detailed bug reports.

It looks like block 263567 contains the problematic transaction with the HODL'd date in the past. For reasons I'm not yet clear on, some systems running v3.0.0 seem to accept this and others not (maybe particularly MACs?)

First thing to try, if you're compiling yourself is to use the master branch which contains a fix, and not the 3.0.0 release.
https://github.com/HOdlcoin/HOdlcoin/tree/HODLCoin0.11.3

Clearly we need a new release with this fix asap at this point. I'll finalize this shortly.

I am not sure how to compile myself on a Mac. If someone can guide me I'll give it a shot.