Answer the question
In order to leave comments, you need to log in
Bitcoin fork, wallet not working, why?
I can’t understand the reason, the wallet is loading endlessly here are the logs
2018-08-04 01:01:06 * Using 8.0MiB for chain state
database up to 286.1MiB of unused mempool space)
2018-08-04 01:01:06 init message: Loading block index...
2018-08-04 01:01:06 Opening LevelDB in /home/slavik/.investcoin/blocks /index
2018-08-04 01:01:09 Opened LevelDB successfully
2018-08-04 01:01:09 Using obfuscation key for /home/slavik/.investcoin/blocks/index: 0000000000000000
2018-08-04 01:01:09 ERROR: LoadBlockIndexGuts: CheckProofOfWork failed : CBlockIndex (pprev = 0, nHeight = 0, = b299a34d310c6fd4fa105528a6e77833a037e6de53b69afb62d613682fd6b2bc Merkle, hashBlock e49d667bd58a6dfc9ca65e087db8f4f48e390dd03bf53ed6dd4dab427df81e3e =)
08.04.2018 01:01:12 the init message: Load index blocks...
2018-08-04 01:01:12 Wiping LevelDB in
/home/slavik/.investcoin/blocks/index /index
2018-08-04 01:01:12 Opened LevelDB successfully
2018-08-04
01:01:12 :12 Initializing databases...
2018-08-04 01:01:12 Wiping LevelDB in /home/slavik/.investcoin/chainstate
2018-08-04 01:01:15 Opening LevelDB in /home/slavik/.investcoin/chainstate
2018-08-04 01:01:17 Opened LevelDB successfully
2018-08-04 01:01:17 Wrote new obfuscate key for /home/slavik/.investcoin/chainstate:
2f0ebd63211c8da2
2018-08-04
01:01:17
-08-04 01:01:17 init message: Loading wallet...
2018-08-04 01:01:17 nFileVersion = 160000
2018-08-04 01:01:17 Keys: 2001 plaintext, 0 encrypted, 2001 w / metadata, 2001 total
2018-08-04 01:01:18 wallet 1689ms
2018-08-04 01:01:18 setKeyPool.size() = 2000
2018-08-04 01:01:18 mapWallet.size() = 0
2018-08-04 01:01:18 mapAddressBook.size() = 0
2018-08-04 01:01:18 Reindexing block file blk00000.dat
... high-hash, proof of work failed (code 16)
2018-08-04 01:01:19 Reindexing finished
2018-08-04 01:01:19 Imported mempool transactions from disk: 0 succeeded, 0 failed, 0 expired, 0 already there
2018-08-04 01:04:35 Shutdown: In progress...
2018-08-04 01:04:35 scheduler thread interrupt
2018-08-04 01:04:35 Dumped mempool: 7e-06s to copy , 0.041282s to dump
2018-08-04 01:04:35 Shutdown: done
up to this point everything works without errors
Answer the question
In order to leave comments, you need to log in
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question