Bitcoin Taproot Scriptpath Spending: What the Chain Reveals
Scriptpath spending exposes your Merkle tree depth to every node operator. The mechanics, the fingerprinting risk, and what wallet developers are missing.
№ 002BitcoinBitcoin 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.
№ 003BitcoinTaproot On-Chain: Keypath vs Scriptpath Spending
A Taproot output looks uniform until it's spent. The witness field reveals exactly which path was taken, and how much it exposes about your setup.
№ 004BitcoinTaproot's Fix for Bitcoin Witness Malleability
Taproot commits every spending script into the output's public key at creation, closing the script-substitution gap SegWit left open.
№ 005BitcoinBitcoin Taproot Internal Key Commitment Explained
Taproot's internal key commitment binds script paths at construction, making retroactive invention mathematically impossible. The precise mechanism, examined.
№ 006BitcoinBitcoin Taproot Key Path Spending and Script Privacy
Taproot key path spending makes complex Bitcoin contracts indistinguishable from simple payments. The mechanism, the limits, and why adoption breadth matters.
№ 007BitcoinBitcoin Script Clean Stack Rule and Taproot Witness Discount
How Bitcoin's clean stack rule shapes Taproot witness discount calculations, with a concrete worked example of script weight and fee math.
№ 008BitcoinBitcoin Script Clean Stack Rules in Tapscript
How Bitcoin's clean stack rule works after Tapscript execution, why it differs from legacy Script, and what it means for spending conditions.
№ 009BitcoinBitcoin'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.
№ 010BitcoinBitcoin'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.
№ 011BitcoinBitcoin 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.
№ 012BitcoinBitcoin Tapscript: Conditional Spending, Hidden Branches
Tapscript lets Bitcoin transactions spend one condition while keeping all others permanently hidden. The exact mechanism, with a worked example.