Bitcoin Core Wallet hasn't synced since fork

[denverminehigh]

Bitcoin Core Wallet wont sync since the fork. Seams to be something about invalid headers. Was wondering if someone could help me out. I posted the debug file below. Thanks in advance



2017-08-07 17:38:13 Bitcoin version v0.14.2
2017-08-07 17:38:13 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-08-07 17:38:14 Assuming ancestors of block 00000000000000000013176bf8d7dfeab4e1db31dc93bc311b436e82ab226b90 have valid signatures.
2017-08-07 17:38:14 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..."
2017-08-07 17:38:14 Default data directory C:\Users\johnj\AppData\Roaming\Bitcoin
2017-08-07 17:38:14 Using data directory C:\Users\johnj\AppData\Roaming\Bitcoin
2017-08-07 17:38:14 Using config file C:\Users\johnj\AppData\Roaming\Bitcoin\bitcoin.conf
2017-08-07 17:38:14 Using at most 125 automatic connections (2048 file descriptors available)
2017-08-07 17:38:14 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements
2017-08-07 17:38:14 Using 4 threads for script verification
2017-08-07 17:38:14 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2017-08-07 17:38:14 Using wallet wallet.dat
2017-08-07 17:38:14 init message: Verifying wallet...
2017-08-07 17:38:14 scheduler thread start
2017-08-07 17:38:14 CDBEnv::Open: LogDir=C:\Users\johnj\AppData\Roaming\Bitcoin\database ErrorFile=C:\Users\johnj\AppData\Roaming\Bitcoin\db.log
2017-08-07 17:38:14 Bound to [::]:8333
2017-08-07 17:38:14 Bound to 0.0.0.0:8333
2017-08-07 17:38:14 Cache configuration:
2017-08-07 17:38:14 * Using 2.0MiB for block index database
2017-08-07 17:38:14 * Using 8.0MiB for chain state database
2017-08-07 17:38:14 * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2017-08-07 17:38:14 init message: Loading block index...
2017-08-07 17:38:14 Opening LevelDB in C:\Users\johnj\AppData\Roaming\Bitcoin\blocks\index
2017-08-07 17:38:14 Opened LevelDB successfully
2017-08-07 17:38:14 Using obfuscation key for C:\Users\johnj\AppData\Roaming\Bitcoin\blocks\index: 0000000000000000
2017-08-07 17:38:14 Opening LevelDB in C:\Users\johnj\AppData\Roaming\Bitcoin\chainstate
2017-08-07 17:38:14 Opened LevelDB successfully
2017-08-07 17:38:14 Using obfuscation key for C:\Users\johnj\AppData\Roaming\Bitcoin\chainstate: 947e0a8f6a3a73d8
2017-08-07 17:38:21 LoadBlockIndexDB: last block file = 953
2017-08-07 17:38:21 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=134, size=96811620, heights=478496...478636, time=2017-08-01...2017-08-02)
2017-08-07 17:38:21 Checking all blk files are present...
2017-08-07 17:38:21 LoadBlockIndexDB: transaction index disabled
2017-08-07 17:38:21 LoadBlockIndexDB: hashBestChain=000000000000000001226f9c0b80f445953fe6a02df662be87510891847471cd height=478636 date=2017-08-02 01:07:22 progress=0.993579
2017-08-07 17:38:21 init message: Rewinding blocks...
2017-08-07 17:38:23 init message: Verifying blocks...
2017-08-07 17:38:23 Verifying last 6 blocks at level 3
2017-08-07 17:38:23 [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE].
2017-08-07 17:38:29 No coin database inconsistencies in last 7 blocks (5426 transactions)
2017-08-07 17:38:29  block index           14968ms
2017-08-07 17:38:29 init message: Loading wallet...
2017-08-07 17:38:29 nFileVersion = 140600
2017-08-07 17:38:29 Keys: 0 plaintext, 205 encrypted, 205 w/ metadata, 205 total
2017-08-07 17:38:29  wallet                   53ms
2017-08-07 17:38:29 setKeyPool.size() = 101
2017-08-07 17:38:29 mapWallet.size() = 5
2017-08-07 17:38:29 mapAddressBook.size() = 4
2017-08-07 17:38:29 mapBlockIndex.size() = 478658
2017-08-07 17:38:29 nBestHeight = 478636
2017-08-07 17:38:29 torcontrol thread start
2017-08-07 17:38:29 AddLocal([2001:0:9d38:90d7:28e1:11af:9d0a:7112]:8333,1)
2017-08-07 17:38:29 Discover: DESKTOP-M9F27DB - 2001:0:9d38:90d7:28e1:11af:9d0a:7112
2017-08-07 17:38:29 init message: Loading addresses...
2017-08-07 17:38:29 Loaded 65633 addresses from peers.dat  387ms
2017-08-07 17:38:29 init message: Loading banlist...
2017-08-07 17:38:29 init message: Starting network threads...
2017-08-07 17:38:29 net thread start
2017-08-07 17:38:29 init message: Done loading
2017-08-07 17:38:29 dnsseed thread start
2017-08-07 17:38:29 opencon thread start
2017-08-07 17:38:29 addcon thread start
2017-08-07 17:38:29 msghand thread start
2017-08-07 17:38:29 GUI: Platform customization: "windows"
2017-08-07 17:38:29 GUI: PaymentServer::LoadRootCAs: Loaded  40  root certificates
2017-08-07 17:38:30 ProcessMessages(version, 122 bytes) FAILED peer=0
2017-08-07 17:38:31 receive version message: /Satoshi:0.14.2/UASF-Segwit:1.0(BIP148)/: version 70015, blocks=479532, us=98.245.142.237:55073, peer=1
2017-08-07 17:38:31 ERROR: AcceptBlockHeader: block 000000000000000000102b57d98d471df579a4c65c9356907b9c1d39ef8f5c0a is marked invalid
2017-08-07 17:38:31 ERROR: invalid header received
2017-08-07 17:38:31 ProcessMessages(headers, 72660 bytes) FAILED peer=1
2017-08-07 17:38:31 receive version message: /Satoshi:0.14.2/: version 70015, blocks=479532, us=98.245.142.237:55075, peer=2
2017-08-07 17:38:40 P2P peers available. Skipped DNS seeding.
2017-08-07 17:38:40 dnsseed thread exit
2017-08-07 17:38:41 Imported mempool transactions from disk: 7386 successes, 0 failed, 0 expired
2017-08-07 17:38:48 receive version message: /Satoshi:0.14.1/: version 70015, blocks=479532, us=98.245.142.237:55083, peer=3
2017-08-07 17:38:49 receive version message: /Satoshi:0.14.1/: version 70015, blocks=479532, us=98.245.142.237:55084, peer=4
2017-08-07 17:38:50 receive version message: /Satoshi:0.14.0/: version 70015, blocks=479532, us=98.245.142.237:55085, peer=5
2017-08-07 17:38:56 receive version message: /Satoshi:0.14.2/: version 70015, blocks=479532, us=[2001:0:9d38:90d7:28e1:11af:9d0a:7112]:55087, peer=6
2017-08-07 17:38:57 receive version message: /Satoshi:0.14.2/UASF-Segwit:1.0(BIP148)/: version 70015, blocks=479532, us=98.245.142.237:55089, peer=7
2017-08-07 17:39:04 receive version message: /Satoshi:0.14.1/UASF-Segwit:0.3(BIP148)/: version 70015, blocks=479532, us=98.245.142.237:55091, peer=8
2017-08-07 17:39:15 receive version message: /Satoshi:0.14.1/: version 70015, blocks=479532, us=98.245.142.237:55095, peer=9
2017-08-07 17:39:21 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2017-08-07 17:39:22 receive version message: /Satoshi:1.14.5(2x)/: version 70015, blocks=479532, us=98.245.142.237:55099, peer=11
2017-08-07 17:40:32 ERROR: AcceptBlockHeader: block 000000000000000000102b57d98d471df579a4c65c9356907b9c1d39ef8f5c0a is marked invalid
2017-08-07 17:40:32 ERROR: invalid header received
2017-08-07 17:40:32 ProcessMessages(headers, 72660 bytes) FAILED peer=1
2017-08-07 17:40:32 ERROR: AcceptBlockHeader: block 000000000000000000102b57d98d471df579a4c65c9356907b9c1d39ef8f5c0a is marked invalid
2017-08-07 17:40:32 ERROR: invalid header received
2017-08-07 17:40:32 ProcessMessages(headers, 72660 bytes) FAILED peer=7
2017-08-07 17:40:33 ERROR: AcceptBlockHeader: block 000000000000000000102b57d98d471df579a4c65c9356907b9c1d39ef8f5c0a is marked invalid
2017-08-07 17:40:33 ERROR: invalid header received
2017-08-07 17:40:33 ProcessMessages(headers, 72660 bytes) FAILED peer=6
2017-08-07 17:40:33 ERROR: AcceptBlockHeader: block 000000000000000000102b57d98d471df579a4c65c9356907b9c1d39ef8f5c0a is marked invalid
2017-08-07 17:40:33 ERROR: invalid header received
2017-08-07 17:40:33 ProcessMessages(headers, 72660 bytes) FAILED peer=9
2017-08-07 17:40:33 ERROR: AcceptBlockHeader: block 000000000000000000102b57d98d471df579a4c65c9356907b9c1d39ef8f5c0a is marked invalid
2017-08-07 17:40:33 ERROR: invalid header received
2017-08-07 17:40:33 ProcessMessages(headers, 72660 bytes) FAILED peer=5
2017-08-07 17:40:33 ERROR: AcceptBlockHeader: block 000000000000000000102b57d98d471df579a4c65c9356907b9c1d39ef8f5c0a is marked invalid
2017-08-07 17:40:33 ERROR: invalid header received
2017-08-07 17:40:33 ProcessMessages(headers, 72660 bytes) FAILED peer=11
2017-08-07 17:40:33 ERROR: AcceptBlockHeader: block 000000000000000000102b57d98d471df579a4c65c9356907b9c1d39ef8f5c0a is marked invalid
2017-08-07 17:40:33 ERROR: invalid header received
2017-08-07 17:40:33 ProcessMessages(headers, 72660 bytes) FAILED peer=3
2017-08-07 17:40:35 ERROR: AcceptBlockHeader: block 000000000000000000102b57d98d471df579a4c65c9356907b9c1d39ef8f5c0a is marked invalid
2017-08-07 17:40:35 ERROR: invalid header received
2017-08-07 17:40:35 ProcessMessages(headers, 72660 bytes) FAILED peer=2

[ranochigo]

Block "000000000000000000102b57d98d471df579a4c65c9356907b9c1d39ef8f5c0a" is a valid block on the Bitcoin main chain, its likely not an issue that is caused by the fork.

There are three possible reasons:
1. Your peers are deliberately sending you malformed blocks for some reason. Try go to Help>Debug Window> Console and key in

Code:

addnode 188.68.53.44 add

2. Your ISP has made your internet connection drop packets coming from Bitcoin nodes.
3. Your blockchain is corrupted. Go to your folder where Bitcoin Core store blocks and delete everything EXCEPT WALLET.DAT. This will result in your client synchronizing all the way from the start.

[HCP]

Did you happen to install BitcoinABC at all? I believe that if you use the default settings during install, it will install to the default BitcoinCore directory... If you installed it and opened it, it may have messed up your Bitcoin Core install

[denverminehigh]

Thanks for the replies. I was able to recover it to Electrum. It was because I installed BitcoinABC. Lesson learned. Gonna use electrum from here anyways. Thanks for all the help!

[CryptoGeo]

Hey guys, i had installed the bitcoin ABC wallet during the time of the fork and seems that my bitcoin core is messed up too. It is unsynchronized since the date of the fork.
Any tips what i should do here?
Cheers

[HCP]

You'll probably need to resync your Core from scratch as it is likely that your ABC install has "corrupted" the blocks in your Core data directory by writing BCC blocks into it.

If you want to continue to use Core and ABC, you'll need to take steps to separate them to prevent this happening again. For instance, use different "datadir" for each application to keep blocks folders and wallet files separate.