BIP 132 Committee-Based BIP Acceptance Explained
BIP 132 committee acceptance explained as a closed governance proposal using four stakeholder segments, timed reviews and a 70% threshold.
Within Blog Posts & Articles
BIP 132 committee acceptance explained as a closed governance proposal using four stakeholder segments, timed reviews and a 70% threshold.
BIP 122 blockchain URI explained: learn its chain IDs, transaction, block and address paths, parser boundaries and safe explorer handling.
BIP 123 classification explained: distinguish consensus, peer services, API/RPC and application layers and apply the right interoperability evidence.
BIP 106 dynamic block size explained: compare its utilisation-only and fee-aware algorithms, 2,016-block periods and hard-fork risks.
BIP 105 block size retargeting explained as a closed hard-fork proposal using coinbase votes, proof-of-work penalties and 2,016-block medians.
BIP 111 NODE_BLOOM explained: understand service-bit discovery, protocol version 70011, legacy SPV compatibility, privacy and node DoS controls.
BIP 113 median time past explained: learn how the previous 11 blocks govern time-based nLockTime, mempool policy and CSV deployment.
BIP 112 CHECKSEQUENCEVERIFY made simple. See what the proposal changes, its current status and what it means for Bitcoin users and operators.
BIP 120 proof of payment explained as a closed transaction-shaped credential, including nonce binding, validation, replay and privacy risks.
BIP 121 btcpop URI explained as a closed proof-of-payment request format with destination, nonce and optional transaction hints.
BIP 103 technology-growth block size explained as a closed hard-fork formula using median time, 17.7% annual growth and scaled sigops.
BIP 101 larger blocks explained as a closed hard-fork schedule starting at 8 MB, doubling every two years and carrying node split risk.