A Bitcoin BIP, or Bitcoin Improvement Proposal, is the formal document used to propose changes to the Bitcoin protocol. Every significant feature added to Bitcoin in the past decade, from SegWit addresses to Schnorr signatures, started life as a BIP. Understanding how this process works gives beginners a clearer picture of why Bitcoin changes so slowly and why that caution is a feature, not a flaw.
What a BIP actually is
A BIP is a written specification, submitted to the Bitcoin development community, that describes a proposed change to Bitcoin's rules, codebase, or processes. The format was adapted from Python's PEP (Python Enhancement Proposal) system and introduced in 2011 by developer Amir Taaki. BIP-0001 was the document that defined the BIP process itself.
Each BIP gets a unique number. BIP 141 introduced Segregated Witness (SegWit). BIP 340, BIP 341, and BIP 342 together defined the Taproot upgrade that introduced Bitcoin Schnorr signatures. BIP 32 established hierarchical deterministic wallets, which is the technology behind Bitcoin derivation paths. The numbering is sequential but not all numbers are used; some proposals are withdrawn or rejected.
The three types of BIPs
BIPs fall into three categories, and the distinction matters:
- Standards Track BIPs propose changes to the Bitcoin protocol itself, including consensus rules, network communication, and transaction formats. These require the broadest agreement across the network and are the most consequential.
- Informational BIPs describe guidelines, design decisions, or general information without proposing a protocol change. They don't require community consensus to be accepted.
- Process BIPs propose changes to how Bitcoin development is organised, including how BIPs themselves are managed.
How a BIP moves from idea to implementation
The process starts with a draft. Anyone can write one. The author shares the idea on the Bitcoin development mailing list or on GitHub, where other developers critique the technical merits, security implications, and potential unintended consequences. This stage can last months or years.
If the draft is technically sound, a BIP editor assigns it a number and the status moves to "Proposed". The editors are not gatekeepers with veto power; they handle formatting and process, not technical approval. Real approval happens through rough consensus across developers, miners, node operators, and businesses.
From "Proposed", a BIP can reach "Final" if it's widely deployed, "Replaced" if a better proposal supersedes it, "Withdrawn" if the author pulls it, or "Rejected" if the community decides against it. There's no central authority that makes these calls. It's a messy, deliberate process by design.
Why consensus is so hard to achieve
Bitcoin has no CEO, no board, and no company controlling it. A BIP that changes consensus rules, the fundamental laws of what counts as a valid block, requires near-universal agreement from miners who build blocks, full node operators who enforce rules, and users who transact. Miss any of those groups and you risk a chain split.
The 2017 SegWit activation illustrated this clearly. The technical BIP was ready well before miners activated it. A prolonged standoff between different factions led to a hard fork (Bitcoin Cash) and a contentious soft fork activation. The experience shaped how developers approach signalling mechanisms today.
This is also why a Bitcoin soft fork differs from a hard fork in consequence. A soft fork tightens existing rules, so old nodes stay compatible. A hard fork loosens or replaces rules, potentially splitting the chain. Most BIPs target soft forks precisely because the risk of a split is lower.
Miner signalling and node enforcement
For Standards Track BIPs that change consensus rules, activation typically uses a signalling mechanism. BIP 9 introduced version bits signalling, where miners include a bit in block headers to indicate readiness. If a threshold percentage of blocks (usually 95%) signals within a defined window, the upgrade locks in.
BIP 8 offered a variation that added a flag day: if signalling thresholds aren't met, nodes can activate anyway after a set block height. Taproot used a variation called Speedy Trial, which set a shorter signalling window with a mandatory lock-in if the threshold was met. It activated in November 2021 at block height 709,632.
Miners signal readiness, but it's full nodes that actually enforce new rules. A miner can signal support and then produce invalid blocks. Full nodes will reject those blocks regardless of miner signals. This is why running a full node matters: it's how individual participants enforce their preferred rule set.
What BIPs mean for everyday Bitcoin holders
Most BIPs never directly affect how you send or receive Bitcoin. But some do change what address types are available, how fees are calculated, or how wallets interact with the network. BIP 32 changed how wallets are backed up. BIP 173 introduced bech32 addresses, which are the lowercase "bc1" addresses you see on most modern wallets today.
When a BIP changes address formats or transaction structures, wallet software has to update. If your wallet is out of date, you might not be able to receive funds sent to a newer address type, or you might pay higher fees than necessary. Keeping wallet software current is the simplest way to stay compatible with network upgrades.
The BIP process is slow on purpose. Bitcoin holds real value for real people, and a protocol bug introduced by a rushed upgrade could cause permanent financial harm with no recourse. The deliberate pace reflects the stakes, not a lack of ambition among developers.
You can browse all published BIPs directly on the official Bitcoin BIPs repository on GitHub, where each document lists its current status, champion, and full technical specification.