Invalid block 784121

000000000000000000046a2698233ed93bb5e74ba7d2146a68ddb0c2504c980d

Why it is invalid

rule and Core reject
bad-blk-sigops
Core check
ConnectBlock
CI checks
A complete block at mainnet height 481824 or later, authenticated previous transactions for every external input, and calculated BIP16/BIP141 sigop cost above 80000.

Incident note: 783426 and 784121 - F2Pool sigops (2023)

Both blocks exceed the sigop limit: accurate sigop cost 80003 against the 80000 maximum, counted in ConnectBlock. The context-free legacy count is under the limit, which is why replay cannot reproduce bad-blk-sigops. Documented in b10c observation 11. CI reproduces the 80003 cost for each block using previous transactions authenticated against its inputs. Block 783426 has 74520 legacy cost, 160 P2SH cost and 5323 witness cost; block 784121 has 72204, 908 and 6891 respectively. The previous transactions are fetched from public APIs and cached; the block bodies and their witness commitments supply the remaining evidence.

Header

version
0x20310000 (540082176)
previous block
00000000000000000004ef043082d84196e3845c9628ee20764c591c1fb29d6c (canonical, mempool.space)
merkle root
3bf92f16ab88b82c8a23f3956075579c3d0fcdff4e8680eeebfdbf6a1eff5b5a
time
2023-04-06 00:56:48 UTC (1680742608)
bits
0x1706023e difficulty 46,843,400,286,277
nonce
1525312513
header hex
000031206c9db21f1c594c7620ee28965c84e39641d8823004ef040000000000000000005a5bff1e6abffdebee80864effcd0f3d9c57756095f3238a2cb888ab162ff93bd0182e643e020617016cea5a

Evidence on file full block

full block
784121-000000000000000000046a2698233ed93bb5e74ba7d2146a68ddb0c2504c980d.bin 1,711,401 bytes
record
data/invalid-blocks.jsonl, line 167

Context

pool
F2Pool by tag
coinbase_height
784121
coinbase_scriptsig_hex
03f9f60b2cfabe6d6df25b386d041b6a6ecf202e73afd2bf8d3422cb2f6e9c9975fdc4c37a958136fd10000000f09f909f092f4632506f6f6c2f730000000000000000000000000000000000000000000000000000000000000000000000050045010000
scriptSig as text
····,··mm·[8m··jn· .s····4"·/n··u···z··6··········/F2Pool/s·····································E···

Observations (6)

Where the block was seen or recovered. Observations record acquisition; they do not establish the failure.