3

Early blocks contain OP_PUSHBYTES sequences in the coinbase input ScriptSig:

  • Block 1: OP_PUSHBYTES_4 ffff001d OP_PUSHBYTES_1 04
  • Block 2: OP_PUSHBYTES_4 ffff001d OP_PUSHBYTES_1 0b
  • Block 3: OP_PUSHBYTES_4 ffff001d OP_PUSHBYTES_1 0e
  • Block 4: OP_PUSHBYTES_4 ffff001d OP_PUSHBYTES_1 1a

Do we know why?

Casey Rodarmor
  • 524
  • 2
  • 9

1 Answers1

3

As mentioned here, ffff001d is the "bits" (representing the current difficulty target), and the rest is called the "extra nonce", used to add more possibilities for mining than just the nonce field. This is also discuss here: ScriptSig (coinbase) structure of the Genesis Block

Later, BIP 34 required that the coinbase include the block height, but this doesn't happen until after block 227,835.

Murch
  • 71,155
  • 33
  • 180
  • 600
meshcollider
  • 11,695
  • 4
  • 24
  • 52
  • I'm really surprised to learn that the very first block had extra nonce space, I always assumed that the extra nonce space was needed later, when the difficulty got very high. It makes me wonder why satoshi didn't allocate another few bytes in the header to nonce space. Does anyone know why the difficulty target was included? – Casey Rodarmor Jan 25 '22 at 17:54