BIP 140 Normalized TXID Explained
BIP 140 normalized TXIDs explained: learn how the closed proposal removed signature scripts, introduced OP_CHECKSIGEX and tracked two identities.
Within Blog Posts & Articles
BIP 140 normalized TXIDs explained: learn how the closed proposal removed signature scripts, introduced OP_CHECKSIGEX and tracked two identities.
BIP 107 dynamic block size explained as a closed hard-fork proposal with a staged runway, 4,032-block checks and 10% increases.
BIP 132 committee acceptance explained as a closed governance proposal using four stakeholder segments, timed reviews and a 70% threshold.
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 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.
BIP 100 dynamic block-size voting explained as a closed hard-fork proposal with 75% miner thresholds, 5% adjustment limits and split risk.
BIP 64 getutxo explained as a closed peer query for UTXO status, including bitmap responses, unauthenticated results, privacy and DoS risks.