Bitcoin Taproot Leaf Version: Future-Proofing Scripts
The leaf version field reserves space for new Bitcoin script rules without a hard fork, the exact mechanism, the constraints, and what it enables.
№ 002BitcoinBitcoin Covenants: Introspection vs Template Approaches
Bitcoin's covenant debate splits on one question: how much can a script inspect its own transaction? A clear breakdown of both camps.
№ 003BitcoinBitcoin Compact Blocks and Mempool Divergence Explained
Compact block reconstruction stalls when mempools diverge. This piece traces the exact failure cascade, the 85% overlap threshold, and what miners do about it.
№ 004BitcoinBitcoin Erlay: Set Reconciliation Explained
Erlay replaces Bitcoin's flood-based INV announcements with set reconciliation, cutting transaction bandwidth roughly 40% without sacrificing propagation speed.
№ 005BitcoinBitcoin's Taproot Annex: Protocol Extensions Explained
The Taproot annex sits consensus-valid but relay-blocked inside every Taproot input, a reserved extension point whose format and uses are still being settled.
№ 006BitcoinBitcoin Erlay: Peer Selection and Mempool Privacy
Erlay cuts Bitcoin's relay bandwidth by ~84%. The peer selection logic, decided before any transaction data exists, is where the privacy argument lives.
№ 007BitcoinBitcoin's Taproot Annex: Reserved Space Explained
The Taproot annex is a reserved byte field in Bitcoin transactions, committed at signing, consensus-valid today, and blank until a future soft fork fills it.
№ 008BitcoinBitcoin Covenant Proposals: Miner Trust and Recursion
CTV, CSFS, and MATT draw the line between allowed and forbidden differently, and each encodes a distinct bet on miner honesty and script recursion.
№ 009BitcoinBitcoin Output Script Versioning and Covenant Enforcement
How Bitcoin's script versioning lets developers add spending rules without breaking old nodes. The mechanics, tradeoffs, and a worked example.
№ 010BitcoinBitcoin Erlay Protocol: Cutting Node Bandwidth by 40%
Erlay uses set reconciliation to cut Bitcoin node bandwidth ~40%. The mechanism, a worked example, and an honest account of the latency trade-off.
№ 011BitcoinBitcoin Locktime and Sequence Numbers Explained
How Bitcoin's locktime field and sequence numbers combine to create relative timelocks. The mechanics, a worked example, and one common misconception.
№ 012BitcoinBitcoin Signet: Controlled Testing Without Testnet Chaos
Signet replaces proof-of-work with a signature check, giving Bitcoin developers stable block times and reproducible test conditions. The mechanism, examined.