BitcoinMachine
TERM_DEF // UPGRADES_BIPS / BIP_1_BIP_PURPOSE_GUIDELINES
BIP 1 (BIP
PURPOSE & GUIDELINES)
BIP 1 (BIP Purpose & Guidelines). The meta-spec describing what BIPs are and how to author them.

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_1_BIP_PURPOSE_GUIDELINES_IS
BIP 1 (BIP Purpose & Guidelines) — at a glance
UPGRADES
BIP 1 — "BIP Purpose & Guidelines" is a proposal in the Process family, first published in 2011 with status replaced. The meta-spec describing what BIPs are and how to author them. Its technical mechanism: defines the BIP document format, headers, and editorial workflow. every BIP after BIP-1 follows its template
Why it exists
DESIGN
BIP 1 (BIP Purpose & Guidelines) exists to solve a specific problem: standardise how Bitcoin protocol changes are proposed and reviewed. 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-1 is the single source of truth for this concern, so any new client built today can match the behaviour of every client built since 2011.
HOW_IT_WORKS
Mechanism
HOW IT WORKS
Mechanically, BIP-1 defines the BIP document format, headers, and editorial workflow. Adoption today: every BIP after BIP-1 follows its template.
1. Author drafts BIP-1 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-1) 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-1 is promoted to "final"; deprecated proposals get "replaced" or "withdrawn".
WORKED_EXAMPLE
BIP-1 — quick reference card
EXAMPLE
BIP number : 1 Title : BIP Purpose & Guidelines Area : Process First published: 2011 Status : replaced Fork class : no Motivation : standardise how Bitcoin protocol changes are proposed and reviewed. Mechanism : defines the BIP document format, headers, and editorial workflow. Where it shows up : every BIP after BIP-1 follows its template. Read the spec : https://github.com/bitcoin/bips/blob/master/bip-0001.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-1 means the same thing across every wallet, miner, and node that has read this spec.
NON-CONSENSUS
BIP-1 is not a consensus rule — clients can implement it without coordinating with the network at large.
SUPERSEDED
BIP-1 is no longer active — either replaced by a later BIP or rejected after review.
COMMON_PITFALLS
Things that catch people out
PITFALLS
  • BIP-1 is no longer active. If you read it in a tutorial, double-check whether the actual current spec is a later BIP.
  • 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 1 (BIP Purpose & Guidelines)
The meta-spec describing what BIPs are and how to author them.
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.