Timechain
Search Donate
Sponsors
Cake Wallet, private Bitcoin and Monero walletSideShift.ai, no-signup crypto exchangeOrangeRock, non-custodial bitcoin spot and perps tradingBraiins Hashpower, buy and sell Bitcoin hashrateLayer Two Labs, drivechains for Bitcoin
BIP 34

Block v2, Height in Coinbase

Deployed Activated soft fork Consensus (soft fork) Specification Assigned 2012-07-06

Blocks must include their height in the coinbase; introduced the version-number supermajority upgrade method.

Plain-English summary by Bitcoin Takeover, based on the BIP text.
From the BIP’s abstract

Bitcoin blocks and transactions are versioned binary structures. Both currently use version 1. This BIP introduces an upgrade path for versioned transactions and blocks. A unique value is added to newly produced coinbase transactions, and blocks are updated to version 2.

Read BIP 34 on GitHubFind in explorer

Activated on mainnet

BIP 34 · Height in coinbase — block 227,931, 2013-03-25.

Every block must write its own height into the coinbase. Coinbase transactions became unique, and the first miner-signalled upgrade mechanism was born.

Version supermajority: 750/1,000 then 950/1,000 blocks (version 2)

In Bitcoin Core

The rule that requires blocks to contain their height (number) in the coinbase input, and the introduction of version 2 blocks has been implemented since v0.7.0. The rule took effect for version 2 blocks as of block 224413 (March 5th 2013), and version 1 blocks are no longer allowed since block 227931 (March 25th 2013).

Changelog

  • 2026-11-041.0.4 · clarify encoding for early blocks
  • 2020-11-181.0.3 · clarify that encoding must be minimal
  • 2016-02-051.0.2 · correction to format prediction regarding sign bit
  • 2016-02-011.0.1 · updated to Final, logged activation block
  • 2012-07-061.0.0 · proposed
From the BIP’s own Changelog section.

Authors

Gavin Andresen
Gavin Andresen12 BIPs · Wiki · X

In the Bitcoin Takeover Wiki

0:000:00