Re: ERROR: ConnectBlock(): too many sigops / InvalidChainFound: invalid block=...

I've just found one in my logs as well:

Code:

2023-04-06T00:56:58Z ERROR: ConnectTip: ConnectBlock 000000000000000000046a2698233ed93bb5e74ba7d2146a68ddb0c2504c980d failed, bad-blk-sigops
2023-04-06T00:56:58Z InvalidChainFound: invalid block=000000000000000000046a2698233ed93bb5e74ba7d2146a68ddb0c2504c980d height=784121 log2_work=94.102730 date=2023-04-06T00:56:48Z
2023-04-06T00:56:58Z InvalidChainFound: current best=00000000000000000004ef043082d84196e3845c9628ee20764c591c1fb29d6c height=784120 log2_work=94.102717 date=2023-04-06T00:46:39Z

This is the result of "bitcoin-cli getblock 000000000000000000046a2698233ed93bb5e74ba7d2146a68ddb0c2504c980d":

Code:

{
"hash": "000000000000000000046a2698233ed93bb5e74ba7d2146a68ddb0c2504c980d",
"confirmations": -1,
"height": 784121,
"version": 540082176,
"versionHex": "20310000",
"merkleroot": "3bf92f16ab88b82c8a23f3956075579c3d0fcdff4e8680eeebfdbf6a1eff5b5a",
"time": 1680742608,
"mediantime": 1680738952,
"nonce": 1525312513,
"bits": "1706023e",
"difficulty": 46843400286276.55,
"chainwork": "000000000000000000000000000000000000000044b9330c4d3c5eb4f1bf358a",
"nTx": 1995,
"previousblockhash": "00000000000000000004ef043082d84196e3845c9628ee20764c591c1fb29d6c",
"strippedsize": 762307,
"size": 1711401,
"weight": 3998322,

The full output with tx data is here: block.txt

Interesting, indeed.