Topic: TheHashCoin: scrypt based cryptocurrency built for the medical cannabis industry - page 4. (Read 2025 times)

I am almost done!

Please bear with me, my internet is abhorrently slow right now ... >.<

Great. Thanks

Oh yeah duhhh sorry. I keep forgetting that you're using a precompiled binary. Okay well I am finishing the VM and instructions now so I will post here when I'm finished!

Not sure where to find " thehashcoin/src/consensus/consensus.h document " i downloaded this wallet already compiled from saltpool.

I am creating a linux VM today with all required dependencies pre-installed and all the wallet binaries pre-compiled so that it will be plug and play for you windows folks, so even if your not proficient it will be very very simple. I will let you know when it is finished! And sorry again for the hassle

So long as you still have a copy of the wallet.dat you will be able to import it to the VM.

Also, can you look in you thehashcoin/src/consensus/consensus.h document within the source code for me? I fear you may have the coinbase maturity value still set at the old value which may be contributing to your problems. It should be set at 360.

Ya it's weird, I deleted everything kept a copy of my wallet.dat and reinstalled the wallet still won't sync up. Here are some errors near the end of the debug log.

2018-08-19 10:46:19 ERROR: ConnectBlock: Consensus::CheckTxInputs: d05c41d5a490767edd3ec02378cb472766c0b412bbf61772ca3d8e5ce386d298, bad-txns-premature-spend-of-coinbase, tried to spend coinbase at depth 674 (code 16)
2018-08-19 10:46:19 InvalidChainFound: invalid block=c8a08b516d93315f292e6bed870b63ae039bd1be0f90586a58c5e711de2904d4  height=13428  log2_work=41.011562  date=2018-08-16 12:36:38
2018-08-19 10:46:19 InvalidChainFound:  current best=4579a56fd6c74e122deb518877a2f83636feb3d3e91fdce51b1033b8eec87856  height=13427  log2_work=41.011437  date=2018-08-16 12:24:20
2018-08-19 10:46:19 ERROR: ConnectTip(): ConnectBlock c8a08b516d93315f292e6bed870b63ae039bd1be0f90586a58c5e711de2904d4 failed
2018-08-19 10:46:19 InvalidChainFound: invalid block=c8a08b516d93315f292e6bed870b63ae039bd1be0f90586a58c5e711de2904d4  height=13428  log2_work=41.011562  date=2018-08-16 12:36:38
2018-08-19 10:46:19 InvalidChainFound:  current best=4579a56fd6c74e122deb518877a2f83636feb3d3e91fdce51b1033b8eec87856  height=13427  log2_work=41.011437  date=2018-08-16 12:24:20
2018-08-19 10:46:35 ERROR: AcceptBlockHeader: prev block invalid
2018-08-19 10:46:35 Misbehaving: 162.208.9.51:421 peer=1 (0 -> 100) BAN THRESHOLD EXCEEDED
2018-08-19 10:46:35 ERROR: invalid header received
2018-08-19 10:46:35 ERROR: AcceptBlockHeader: prev block invalid
2018-08-19 10:46:35 Misbehaving: 192.243.103.250:421 peer=0 (0 -> 100) BAN THRESHOLD EXCEEDED
2018-08-19 10:46:35 ERROR: invalid header received
2018-08-19 10:46:35 Warning: not punishing manually-connected peer 192.243.103.250:421!
2018-08-19 10:47:15 ERROR: AcceptBlockHeader: prev block invalid
2018-08-19 10:47:15 Misbehaving: 192.243.103.250:421 peer=0 (100 -> 200)
2018-08-19 10:47:15 ERROR: invalid header received
2018-08-19 10:47:35 ERROR: AcceptBlockHeader: prev block invalid
2018-08-19 10:47:35 Misbehaving: 192.243.103.250:421 peer=0 (200 -> 300)
2018-08-19 10:47:35 ERROR: invalid header received
2018-08-19 10:48:09 ERROR: AcceptBlockHeader: prev block invalid
2018-08-19 10:48:09 Misbehaving: 192.243.103.250:421 peer=0 (300 -> 400)
2018-08-19 10:48:09 ERROR: invalid header received
2018-08-19 10:48:43 Potential stale tip detected, will try using extra outbound peer (last tip update: 144 seconds ago)
2018-08-19 10:49:50 ERROR: AcceptBlockHeader: prev block invalid
2018-08-19 10:49:50 Misbehaving: 192.243.103.250:421 peer=0 (400 -> 500)
2018-08-19 10:49:50 ERROR: invalid header received
2018-08-19 10:50:00 ERROR: AcceptBlockHeader: prev block invalid
2018-08-19 10:50:00 Misbehaving: 192.243.103.250:421 peer=0 (500 -> 600)
2018-08-19 10:50:00 ERROR: invalid header received
2018-08-19 10:50:54 ERROR: AcceptBlockHeader: prev block invalid
2018-08-19 10:50:54 Misbehaving: 192.243.103.250:421 peer=0 (600 -> 700)
2018-08-19 10:50:54 ERROR: invalid header received
2018-08-19 10:50:55 ERROR: AcceptBlockHeader: prev block invalid
2018-08-19 10:50:55 Misbehaving: 192.243.103.250:421 peer=0 (700 -> 800)
2018-08-19 10:50:55 ERROR: invalid header received
2018-08-19 10:51:43 Potential stale tip detected, will try using extra outbound peer (last tip update: 324 seconds ago)

Hmmm.. It appears you must still have some portion of the chain that's invalid somewhere on your system when you're trying to import the chain because I see invalid block errors in the debug.log, and every node I have tried to sync has done so without error. Perhaps you have data for an orphaned block somewhere on your system. Let me know when you're free to play with it again and I will help you figure it out.

sent to your email, have a good night

Also, it appears saltpool is back in sync!

Damn it man, I'm sorry. We will figure it out. I am going to start playing with a wallet on windows to try to pinpoint the issue. Also, could you email me your debug.log to [email protected]?

Still a no go. got a meeting tonight but can try some other things tomorrow. Thanks for your help.

Okay blk.dat has been added in the same folder where the bootstrap was located on the github. I would remove all traces of the bootstrap from the datadir for this first go after adding the blk.dat to the blocks folder. Make sure you delete the current data in the blocks folder. Also added rev.dat (honestly not sure if you need both) .. Also, if you wanted to give using a linux VM a shot, I could walk you through step by step setting up an Ubuntu 16.04 image and getting the wallet compiled with probably less than a dozen commands.

I can try the blk0000.dat. not really proficient in linux

Damn it.. I will try uploading the blk0000.dat to the github for you to download and place in the blocks directory. I guess I will have to make a live boot of Windows 7 to play around with because unfortunately every pc in my house is running a linux distro.

If all else fails, would you be open to running a linux VM using VirtualBox and compiling a wallet within that? I know it's a pain in the ass, but I will stick with you through it.. I want to see you have a working wallet D:

 I did that still no go, it does index so it is loading from bootstrap but when it goes to process it stops at 67%. (should note this is a windows wallet) as well it renames the bootstrap.dat to bootstrap.dat.old

Try deleting everything in your data directory except for your thehashcoin.conf, wallet.dat and the bootstrap.dat

Also I still see headers being sent your way from the seed node..

Did you delete the blocks/chainstate folders and their contents and place the bootstrap.dat in your data directory?

I'm sorry about this, we will get it sorted either way. If this doesn't work for you I will try uploading by actual blk.dat for you.

It indexes the blocks fine but when it goes to process them it stalls out at 67% @block 13277

Added a folder called bootstrap-blk18763 to the github, within is a bootstrap.dat as of block 18763, give it a shot.