Sync Issues with Bitcoin Core and Legacy Addresses

11 replies 447 views
roguesatoshiFull Member
Posts: 34 · Reputation: 558
#1Oct 26, 2019, 08:48 AM
Running Bitcoin Core 20.1 on Ubuntu 24.04. It stops syncing at block 623950 with this error: ConnectBlock failed. Anyone know how to fix this?
4 Reply Quote Share
orbit1337Senior Member
Posts: 434 · Reputation: 941
#2Oct 27, 2019, 02:52 PM
You should really consider upgrading to a newer version. Maybe 0.26? It’s a lot better and still supports legacy wallets.
5 Reply Quote Share
planktonHero Member
Posts: 1284 · Reputation: 2049
#3Oct 28, 2019, 08:01 PM
Pro tip: use code tags in your posts. Makes it easier for everyone to read.
3 Reply Quote Share
roguesatoshiFull Member
Posts: 34 · Reputation: 558
#4Oct 28, 2019, 11:36 PM
Thanks for the tip! But 20.1 is the last version that works with Berkeley DB. I need my old uncompressed addresses... Importing them into the latest version is a mess too.
3 Reply Quote Share
planktonHero Member
Posts: 1284 · Reputation: 2049
#5Oct 29, 2019, 01:07 AM
First merit for being quick on the uptake!
0 Reply Quote Share
whale420Senior Member
Posts: 727 · Reputation: 853
#6Oct 29, 2019, 03:50 AM
Yeah the latest version ditched Berkeley DB for SQLite. Descriptor wallets can’t use importprivkey either. Check the guides here on how to import legacy wallets.
2 Reply Quote Share
0xChadNewbie
Posts: 513 · Reputation: 3
#7Oct 31, 2019, 01:15 AM
That won’t work with compressed WIF keys. You need to use the uncompressed version for legacy addresses.
0 Reply Quote Share
orbit1337Senior Member
Posts: 434 · Reputation: 941
#8Oct 31, 2019, 01:47 AM
I used v26.1.0 with uncompressed addresses just fine. Backup your wallet and give it a shot!
3 Reply Quote Share
roguesatoshiFull Member
Posts: 34 · Reputation: 558
#9Oct 31, 2019, 10:14 PM
Installed version 26, and I got the legacy address added! But man, dealing with that syncing issue was a nightmare.
3 Reply Quote Share
0xChadNewbie
Posts: 513 · Reputation: 3
#10Nov 1, 2019, 04:04 AM
Just a heads up, using the 'combo' descriptor with a WIF key without a compressed flag is pointless. It won't derive the right scripts.
0 Reply Quote Share
roguesatoshiFull Member
Posts: 34 · Reputation: 558
#11Nov 1, 2019, 05:17 AM
I have both compressed and uncompressed WIF keys. In the latest version, I couldn’t add a legacy uncompressed address at all! Had to revert to 20.1 for that.
0 Reply Quote Share
pr0to88Member
Posts: 1222 · Reputation: 235
#12Nov 1, 2019, 10:33 AM
Good on ya for sticking with it. Welcome to the forum, and good luck with your coins!
0 Reply Quote Share

Related topics