Bitcoin Core Stuck at Block 623950

I’m using Bitcoin Core 20.1 from this link https://bitcoincore.org/bin/bitcoin-core-0.20.1 (bitcoin-0.20.1-x86_64-linux-gnu.tar.gz for ubuntu 24.04) with Berkeley DB and I’ve got the prune set to 14000. But it gets stuck syncing at block 623950 and I keep getting this error: ERROR: ConnectBlock: CheckQueue failed InvalidChainFound: invalid block=0000000000000000000b1efa2e2c7e7dfa9800dfd66e90e5efbe5530c803da43 height=623951 I’ve tried a bunch of things like: -reindex-chainstate reconsiderblock Connecting to different peers Deleting chainstate -assumevalid=0 Even did a full -reindex .... If anyone has any ideas, I’d really appreciate your help!

I'd start by upgrading Bitcoin Core to a more recent version. Maybe not the latest, so you're not forced to switch to a descriptor wallet, but 0.26 for instance is a lot newer and still supports legacy wallets.

May I suggest you learn to use the code tag # in the future to reduce text walls down to a scrollable window that is easier to look at.

Thank u for the reply! As far as I know, version 20.1 is the last version that supports Berkeley DB, allowing the addition of legacy uncompressed addresses to the wallet... And even if I import a wallet created with version 20.1 with legacy addresses (non-descriptor) into the latest version of Bitcoin Core, problems arise and there are a lot of workarounds! I would prefer to stick with a version that supports Berkeley DB... Maybe I don't understand something! Let's say, if I have the latest version of Bitcoin Core and I have a compressed WIF... How can I add a legacy uncompressed address for this WIF key through the console? Sorry... I will do it like that in the future

1st merit given for being a quick learner

The latest version no longer supports Berkeley DB; it is already switched to SQlite as the Bitcoin core database backend for the descriptor wallet. but there's a way to import legacy wallet we already have some guides here on the forum. Descriptor wallets do not support using the "importprivkey" command; it only supports legacy wallets. However, like I said, there's a way to import these WIF keys You can try the method provided from this thread: "[HOW-TO] Import privkeys into a Bitcoin Core descriptor wallet"

You can't with that WIF private key. WIF with compressed flag byte (starts with 'L' or 'K') will generate its compressed public key pair; thus, compressed legacy address. If you want to derive the uncompressed legacy address, use its WIF without that flag (starts with '5'). To import using the console (testnet, starts with '9'): Compute the checksum: get the checksum in the result: "zzpvlmvx" To import: Timestamp "now" will prevent the client from rescanning once its imported to the wallet, use a specific unix time value or 0 if you want it to rescan. And if you're expecting P2PK outputs: Checksum: "pxrrw3he" To import:

I'm not sure what database it used, but I can tell you I've used Bitcoin Core v26.1.0 with uncompressed legacy addresses. You can just try it: backup your wallet again (to preserve your latest labels), and upgrade.

Thanks everyone for the help! I installed version 26, and using 'combo', the legacy address was added! As for the glitchy block, I still have a bad aftertaste – spent 4 days dealing with it.

Just take note that "combo" descriptor is pointless on a WIF private key without the compressed flag byte since the other two SegWit output scripts wont be derived from it. Otherwise, it'll be non-standard. You don't have to re-import it as 'pkh' though since it basically did that already, it just skipped the 'wpkh' and 'sh(wpkh)' scripts of the combo descriptor. But I have a feeling that you're actually have a WIF with compressed flag byte and just mistakenly pertaining the legacy address as "legacy uncompressed address". If so, a legacy address can be derived from a compressed or uncompressed public key, not exclusive to uncompressed. If not, disregard this part.

I have both a compressed and an uncompressed WIF private key. On the latest version of Bitcoin Core, no matter what commands I tried , I was only able to add Legacy (Compressed), P2SH-P2WPKH, SegWit, and Taproot... But I couldn't manage to add a Legacy uncompressed address! I took extreme measures and decided to install version 20.1, where I was able to add a Legacy uncompressed address, but I ran into a synchronization issue. With 'combo' in version 26, it worked right away.

Some merits deserved for followup. Plus Politeness and  persistency. Pleasure to have a new person on the forum. Good luck with coins.