BitcoinMachine
TERM_DEF // UPGRADES_BIPS / BIP_23_GETBLOCKTEMPLATE_EXTENSIONS
BIP 23
(GETBLOCKTEMPLATE EXTENSIONS)
BIP 23 (Getblocktemplate Extensions). Extensions to getblocktemplate including coinbase customization.

This page sits in the Upgrades & BIPs section — The proposal process and the major upgrades that shaped Bitcoin. Read on for what it is, why it exists, how it works under the hood, and what to watch out for.
WHAT_BIP_23_GETBLOCKTEMPLATE_EXTENSIONS_IS
BIP 23 (Getblocktemplate Extensions) — at a glance
UPGRADES
BIP 23 — "Getblocktemplate Extensions" is a proposal in the Mining family, first published in 2012 with status final. Extensions to getblocktemplate including coinbase customization. Its technical mechanism: additions to BIP-22 for stale-template avoidance and signed submission. extension to BIP-22, supported by most mining pools
Why it exists
DESIGN
BIP 23 (Getblocktemplate Extensions) exists to solve a specific problem: extend getblocktemplate with longpoll, mutations, and tx submission negotiation. Without a written, numbered spec, every wallet and node implementer would interpret the requirement differently — and Bitcoin's value depends on every implementation agreeing exactly. BIP-23 is the single source of truth for this concern, so any new client built today can match the behaviour of every client built since 2012.
HOW_IT_WORKS
Mechanism
HOW IT WORKS
Mechanically, BIP-23 additions to BIP-22 for stale-template avoidance and signed submission. Adoption today: extension to BIP-22, supported by most mining pools.
1. Author drafts BIP-23 against the BIP-2 template — abstract, motivation, specification, rationale. 2. The text + a reference implementation are posted on the bitcoin-dev list and as a PR to bitcoin/bips. 3. Reviewers tear it apart: ambiguities, security concerns, edge cases, interaction with prior BIPs. 4. Once stable, the BIP editor merges it; it gets a number (BIP-23) and the status "draft" or "proposed". 5. Implementations land in Bitcoin Core / wallets / other clients. For consensus changes: activation parameters chosen. 6. After deployment + adoption, BIP-23 is promoted to "final"; deprecated proposals get "replaced" or "withdrawn".
WORKED_EXAMPLE
BIP-23 — quick reference card
EXAMPLE
BIP number : 23 Title : Getblocktemplate Extensions Area : Mining First published: 2012 Status : final Fork class : no Motivation : extend getblocktemplate with longpoll, mutations, and tx submission negotiation. Mechanism : additions to BIP-22 for stale-template avoidance and signed submission. Where it shows up : extension to BIP-22, supported by most mining pools. Read the spec : https://github.com/bitcoin/bips/blob/master/bip-0023.mediawiki
KEY_PROPERTIES
OPT-IN
No authority can force a BIP on anyone. Adoption depends entirely on whether the change is genuinely useful.
NUMBERED
Stable numeric reference — BIP-23 means the same thing across every wallet, miner, and node that has read this spec.
NON-CONSENSUS
BIP-23 is not a consensus rule — clients can implement it without coordinating with the network at large.
DEPLOYED
Implementations of BIP-23 are in production. The behaviour is observable on mainnet today.
COMMON_PITFALLS
Things that catch people out
PITFALLS
  • Don't confuse "draft" / "proposed" / "final" status — read the BIP header before relying on it in production.
  • The BIP number is just an editorial counter — it doesn't imply correctness or stability. Always cross-reference with the latest bitcoin/bips repo.
RELATED_CONCEPTS
Other terms from Upgrades & BIPs — click any to read its page:
Segregated Witness (SegWit, BIP 141) Taproot (BIP 341) Tapscript (BIP 342) Schnorr (BIP 340) BIP Process Soft Fork Activation MASF (Miner-Activated Soft Fork) UASF (User-Activated Soft Fork)
TERMINOLOGY_INDEX
TERMINOLOGY
BIP 23 (Getblocktemplate Extensions)
Extensions to getblocktemplate including coinbase customization.
Segregated Witness (SegWit, BIP 141)
The 2017 upgrade separating witness-data/">witness data, fixing tx malleability, and introducing weight units.
Taproot (BIP 341)
The 2021 upgrade introducing key-aggregable schnorr-signatures/">Schnorr signatures and Merkleized script trees.
Tapscript (BIP 342)
Script-language updates accompanying Taproot — new opcodes, removed limits.
Schnorr (BIP 340)
The Schnorr signature spec adopted by Taproot.
BIP Process
The community workflow for proposing, discussing, and tracking changes to Bitcoin.
Soft Fork Activation
The mechanism (versionbits, MASF, UASF, Speedy Trial) by which soft forks turn on.
MASF (Miner-Activated Soft Fork)
Activation triggered by miner signaling in block versions.