Bitcoin Core Stuck at Block 623950

[kreosan]

Bitcoin Core 20.1 https://bitcoincore.org/bin/bitcoin-core-0.20.1 (bitcoin-0.20.1-x86_64-linux-gnu.tar.gz // ubuntu 24.04) with Berkeley DB (prune=14000) stops syncing at block 623950 with the following error:
ERROR: ConnectBlock: CheckQueue failed  
InvalidChainFound: invalid block=0000000000000000000b1efa2e2c7e7dfa9800dfd66e90e5efbe5530c803da43 height=623951  

Tried:

-reindex-chainstate
reconsiderblock
Connecting to different peers
Deleting chainstate
-assumevalid=0
A full -reindex ....

Code:

2025-03-12T15:05:55Z UpdateTip: new best=00000000000000000008ab700bbd8c0413ebeb3ac9c67c620bf0310c2f7ca10e height=623944 version=0x37ffe000 log2_work=91.817949 tx=517174209 date='2020-04-01T17:26:54Z' progress=0.500669 cache=444.9MiB(2882282txo)
2025-03-12T15:05:55Z UpdateTip: new best=0000000000000000000706d6f7f39581ff16d31cb9e58082cd78a9c2b05278e8 height=623945 version=0x27ffe000 log2_work=91.817968 tx=517176653 date='2020-04-01T17:35:58Z' progress=0.500671 cache=445.1MiB(2883850txo)
2025-03-12T15:05:55Z UpdateTip: new best=000000000000000000122ec39ee5adcd79e8f247993dc70a90842dfbc3037f0d height=623946 version=0x3fffe000 log2_work=91.817988 tx=517179261 date='2020-04-01T17:37:26Z' progress=0.500673 cache=445.2MiB(2884582txo)
2025-03-12T15:05:56Z UpdateTip: new best=0000000000000000000742f52cba2bec3a1a5b555e4bd04b6d320d39b586c662 height=623947 version=0x20800000 log2_work=91.818008 tx=517181422 date='2020-04-01T17:40:17Z' progress=0.500676 cache=445.2MiB(2884644txo)
2025-03-12T15:05:56Z Pre-allocating up to position 0x800000 in rev02019.dat
2025-03-12T15:05:56Z UpdateTip: new best=0000000000000000000ba251bf6b2f9eb9f12f7db7092f3f7b394733d631d9ec height=623948 version=0x2fffe000 log2_work=91.818028 tx=517182999 date='2020-04-01T17:42:23Z' progress=0.500677 cache=445.5MiB(2887183txo)
2025-03-12T15:05:56Z UpdateTip: new best=000000000000000000113b44d51deb2224807c4afc1badfe92909b4bd328ca9f height=623949 version=0x3fffe000 log2_work=91.818047 tx=517184268 date='2020-04-01T17:46:43Z' progress=0.500678 cache=446.0MiB(2890983txo)
2025-03-12T15:05:56Z UpdateTip: new best=0000000000000000000f2adce67e49b0b6bdeb9de8b7c3d7e93b21e7fc1e819d height=623950 version=0x2000e000 log2_work=91.818067 tx=517186863 date='2020-04-01T18:13:31Z' progress=0.500681 cache=446.4MiB(2894549txo)
2025-03-12T15:05:57Z ERROR: ConnectBlock: CheckQueue failed
2025-03-12T15:05:57Z InvalidChainFound: invalid block=0000000000000000000b1efa2e2c7e7dfa9800dfd66e90e5efbe5530c803da43  height=623951  log2_work=91.818087  date=2020-04-01T18:25:42Z
2025-03-12T15:05:57Z InvalidChainFound:  current best=0000000000000000000f2adce67e49b0b6bdeb9de8b7c3d7e93b21e7fc1e819d  height=623950  log2_work=91.818067  date=2020-04-01T18:13:31Z
2025-03-12T15:05:57Z ERROR: ConnectTip: ConnectBlock 0000000000000000000b1efa2e2c7e7dfa9800dfd66e90e5efbe5530c803da43 failed, block-validation-failed
2025-03-12T15:05:57Z InvalidChainFound: invalid block=0000000000000000000fbc14816a32e9b27495cddf75ac2b7299012bcc0068ae  height=623982  log2_work=91.818699  date=2020-04-01T23:28:09Z
2025-03-12T15:05:57Z InvalidChainFound:  current best=0000000000000000000f2adce67e49b0b6bdeb9de8b7c3d7e93b21e7fc1e819d  height=623950  log2_work=91.818067  date=2020-04-01T18:13:31Z
2025-03-12T15:05:57Z Disconnecting and discouraging peer 16.162.137.92:8333!
2025-03-12T15:05:57Z Pre-allocating up to position 0x3000000 in blk02022.dat
2025-03-12T15:05:58Z Pre-allocating up to position 0x4000000 in blk02022.dat
2025-03-12T15:05:58Z New outbound peer connected: version: 70016, blocks=887484, peer=329 (block-relay)
2025-03-12T15:05:59Z Pre-allocating up to position 0x5000000 in blk02022.dat
2025-03-12T15:05:59Z Pre-allocating up to position 0x6000000 in blk02022.dat
2025-03-12T15:06:00Z Pre-allocating up to position 0x7000000 in blk02022.dat
2025-03-12T15:06:01Z Pre-allocating up to position 0x8000000 in blk02022.dat
2025-03-12T15:06:02Z Leaving block file 2022: CBlockFileInfo(blocks=115, size=133417269, heights=623589...624392, time=2020-03-30...2020-04-04)
2025-03-12T15:06:02Z Pre-allocating up to position 0x1000000 in blk02023.dat
2025-03-12T15:06:03Z Pre-allocating up to position 0x2000000 in blk02023.dat
2025-03-12T15:06:04Z Pre-allocating up to position 0x3000000 in blk02023.dat
2025-03-12T15:06:04Z Pre-allocating up to position 0x4000000 in blk02023.dat
2025-03-12T15:06:05Z Pre-allocating up to position 0x5000000 in blk02023.dat
2025-03-12T15:07:32Z ERROR: AcceptBlockHeader: prev block invalid
2025-03-12T15:07:32Z Disconnecting and discouraging peer 109.224.244.192:8333!
2025-03-12T15:07:32Z ERROR: AcceptBlockHeader: prev block invalid
2025-03-12T15:07:32Z Disconnecting and discouraging peer 188.214.129.26:8333!
2025-03-12T15:07:32Z ERROR: AcceptBlockHeader: prev block invalid
2025-03-12T15:07:32Z Disconnecting and discouraging peer 95.217.160.34:8333!
2025-03-12T15:07:33Z ERROR: AcceptBlockHeader: prev block invalid
2025-03-12T15:07:33Z Disconnecting and discouraging peer 209.237.133.54:8333!

Any help would be greatly appreciated!

[LoyceV]

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.

[NotFuzzyWarm]

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.

Code:

-reindex-chainstate
reconsiderblock
Connecting to different peers
Deleting chainstate
-assumevalid=0
A full -reindex .... Sad

2025-03-12T15:05:55Z UpdateTip: new best=00000000000000000008ab700bbd8c0413ebeb3ac9c67c620bf0310c2f7ca10e height=623944 version=0x37ffe000 log2_work=91.817949 tx=517174209 date='2020-04-01T17:26:54Z' progress=0.500669 cache=444.9MiB(2882282txo)
2025-03-12T15:05:55Z UpdateTip: new best=0000000000000000000706d6f7f39581ff16d31cb9e58082cd78a9c2b05278e8 height=623945 version=0x27ffe000 log2_work=91.817968 tx=517176653 date='2020-04-01T17:35:58Z' progress=0.500671 cache=445.1MiB(2883850txo)
2025-03-12T15:05:55Z UpdateTip: new best=000000000000000000122ec39ee5adcd79e8f247993dc70a90842dfbc3037f0d height=623946 version=0x3fffe000 log2_work=91.817988 tx=517179261 date='2020-04-01T17:37:26Z' progress=0.500673 cache=445.2MiB(2884582txo)
2025-03-12T15:05:56Z UpdateTip: new best=0000000000000000000742f52cba2bec3a1a5b555e4bd04b6d320d39b586c662 height=623947 version=0x20800000 log2_work=91.818008 tx=517181422 date='2020-04-01T17:40:17Z' progress=0.500676 cache=445.2MiB(2884644txo)
2025-03-12T15:05:56Z Pre-allocating up to position 0x800000 in rev02019.dat
2025-03-12T15:05:56Z UpdateTip: new best=0000000000000000000ba251bf6b2f9eb9f12f7db7092f3f7b394733d631d9ec height=623948 version=0x2fffe000 log2_work=91.818028 tx=517182999 date='2020-04-01T17:42:23Z' progress=0.500677 cache=445.5MiB(2887183txo)
2025-03-12T15:05:56Z UpdateTip: new best=000000000000000000113b44d51deb2224807c4afc1badfe92909b4bd328ca9f height=623949 version=0x3fffe000 log2_work=91.818047 tx=517184268 date='2020-04-01T17:46:43Z' progress=0.500678 cache=446.0MiB(2890983txo)
2025-03-12T15:05:56Z UpdateTip: new best=0000000000000000000f2adce67e49b0b6bdeb9de8b7c3d7e93b21e7fc1e819d height=623950 version=0x2000e000 log2_work=91.818067 tx=517186863 date='2020-04-01T18:13:31Z' progress=0.500681 cache=446.4MiB(2894549txo)
2025-03-12T15:05:57Z ERROR: ConnectBlock: CheckQueue failed
2025-03-12T15:05:57Z InvalidChainFound: invalid block=0000000000000000000b1efa2e2c7e7dfa9800dfd66e90e5efbe5530c803da43  height=623951  log2_work=91.818087  date=2020-04-01T18:25:42Z
2025-03-12T15:05:57Z InvalidChainFound:  current best=0000000000000000000f2adce67e49b0b6bdeb9de8b7c3d7e93b21e7fc1e819d  height=623950  log2_work=91.818067  date=2020-04-01T18:13:31Z
2025-03-12T15:05:57Z ERROR: ConnectTip: ConnectBlock 0000000000000000000b1efa2e2c7e7dfa9800dfd66e90e5efbe5530c803da43 failed, block-validation-failed
2025-03-12T15:05:57Z InvalidChainFound: invalid block=0000000000000000000fbc14816a32e9b27495cddf75ac2b7299012bcc0068ae  height=623982  log2_work=91.818699  date=2020-04-01T23:28:09Z
2025-03-12T15:05:57Z InvalidChainFound:  current best=0000000000000000000f2adce67e49b0b6bdeb9de8b7c3d7e93b21e7fc1e819d  height=623950  log2_work=91.818067  date=2020-04-01T18:13:31Z
2025-03-12T15:05:57Z Disconnecting and discouraging peer 16.162.137.92:8333!
2025-03-12T15:05:57Z Pre-allocating up to position 0x3000000 in blk02022.dat
2025-03-12T15:05:58Z Pre-allocating up to position 0x4000000 in blk02022.dat
2025-03-12T15:05:58Z New outbound peer connected: version: 70016, blocks=887484, peer=329 (block-relay)
2025-03-12T15:05:59Z Pre-allocating up to position 0x5000000 in blk02022.dat
2025-03-12T15:05:59Z Pre-allocating up to position 0x6000000 in blk02022.dat
2025-03-12T15:06:00Z Pre-allocating up to position 0x7000000 in blk02022.dat
2025-03-12T15:06:01Z Pre-allocating up to position 0x8000000 in blk02022.dat
2025-03-12T15:06:02Z Leaving block file 2022: CBlockFileInfo(blocks=115, size=133417269, heights=623589...624392, time=2020-03-30...2020-04-04)
2025-03-12T15:06:02Z Pre-allocating up to position 0x1000000 in blk02023.dat
2025-03-12T15:06:03Z Pre-allocating up to position 0x2000000 in blk02023.dat
2025-03-12T15:06:04Z Pre-allocating up to position 0x3000000 in blk02023.dat
2025-03-12T15:06:04Z Pre-allocating up to position 0x4000000 in blk02023.dat
2025-03-12T15:06:05Z Pre-allocating up to position 0x5000000 in blk02023.dat
2025-03-12T15:07:32Z ERROR: AcceptBlockHeader: prev block invalid
2025-03-12T15:07:32Z Disconnecting and discouraging peer 109.224.244.192:8333!
2025-03-12T15:07:32Z ERROR: AcceptBlockHeader: prev block invalid
2025-03-12T15:07:32Z Disconnecting and discouraging peer 188.214.129.26:8333!
2025-03-12T15:07:32Z ERROR: AcceptBlockHeader: prev block invalid
2025-03-12T15:07:32Z Disconnecting and discouraging peer 95.217.160.34:8333!
2025-03-12T15:07:33Z ERROR: AcceptBlockHeader: prev block invalid
2025-03-12T15:07:33Z Disconnecting and discouraging peer 209.237.133.54:8333!

[kreosan]

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.

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?

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.
....

Sorry... I will do it like that in the future

[NotFuzzyWarm]

1st merit given for being a quick learner 

[BitMaxz]

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...

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.

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?

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"

[nc50lc]

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?

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:

Code:

getdescriptorinfo "pkh(91dKmbXPRSVp8vemQPWecCFT1esvSeDHYgpoPexzeTkCuowEeM3)"

get the checksum in the result: "zzpvlmvx"
To import:

Code:

importdescriptors "[{\"desc\": \"pkh(91dKmbXPRSVp8vemQPWecCFT1esvSeDHYgpoPexzeTkCuowEeM3)#zzpvlmvx\",\"label\": \"your_label\",\"timestamp\": \"now\"}]"

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:

Code:

getdescriptorinfo "pk(91dKmbXPRSVp8vemQPWecCFT1esvSeDHYgpoPexzeTkCuowEeM3)"

Checksum: "pxrrw3he"
To import:

Code:

importdescriptors "[{\"desc\": \"pk(91dKmbXPRSVp8vemQPWecCFT1esvSeDHYgpoPexzeTkCuowEeM3)#pxrrw3he\",\"label\": \"your_label\",\"timestamp\": 0}]"

[LoyceV]

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...

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.

[kreosan]

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.

[nc50lc]

Thanks everyone for the help! I installed version 26, and using 'combo', the legacy address was added!

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.

[kreosan]

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.

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.

[philipma1957]

Some merits deserved for followup. Plus Politeness and  persistency.

Pleasure to have a new person on the forum.

Good luck with coins.