<!-- llms-explorer concept facts · https://llms-explorer.com/tree/bitcoin-protocol-and-ecosystem/ · pack 2026-09-08 · ~1888 tokens -->

# Bitcoin protocol and ecosystem

> Bitcoin protocol and ecosystem expert covering base-layer mechanics, network upgrades, and the L2/metaprotocol frontier. Owns: UTXO model, coin selection algorithms; transaction structure (txid vs wtx

Parent: [Blockchain protocols](https://llms-explorer.com/tree/blockchain-protocols/) · 5 facets · 17 facts · page: https://llms-explorer.com/tree/bitcoin-protocol-and-ecosystem/

## Overview

- Bitcoin protocol and ecosystem expert covering base-layer mechanics, network upgrades, and the L2/metaprotocol frontier. Owns: UTXO model, coin selection algorithms; transaction structure (txid vs wtxid, weight/vbytes, implicit-fee derivation); Bitcoin Script and address formats (P2PKH, P2SH, P2WPKH, P2WSH, P2TR, multisig, CLTV/CSV timelocks, bech32/bech32m encoding); block and header structure, Merkle roots; PoW mining, difficulty retargeting, the halving schedule and 21M cap; mempool and fee mechanics (sat/vByte, RBF, CPFP, TRUC/BIP-431); soft-fork history (SegWit, Taproot/Schnorr/MAST) and activation mechanisms; Lightning Network (channel construction, HTLCs, routing, BOLT specifications); ordinals, BRC-20, Runes; BitVM and the Bitcoin-L2 landscape (sidechains, drivechains, covenants, Babylon shared security); full nodes, wallets, UTXO-vs-account model tradeoffs. Route consensus theory to distributed-systems-consensus, cryptography math to blockchain-crypto-primitives, tokenomics to blockchain-economics. — [source](https://llms-explorer.com/sources/mdb-context-hub/bitcoin-protocol-expert/#overview)

## Where this helps

- Explaining why a Bitcoin transaction's fee is calculated in sat/vByte rather than a flat fee, and why weight or vbytes, not raw byte count, determines that cost after SegWit. — [source](https://llms-explorer.com/tree/bitcoin-protocol-and-ecosystem/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)*
- Choosing between address and script formats — P2PKH, P2SH, P2WPKH, P2WSH, P2TR — when designing a wallet or an on-chain contract, since each trades off cost, privacy, and script flexibility differently. — [source](https://llms-explorer.com/tree/bitcoin-protocol-and-ecosystem/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)*
- Understanding why a transaction is stuck unconfirmed in the mempool and evaluating whether Replace-By-Fee or Child-Pays-For-Parent is the right fix. — [source](https://llms-explorer.com/tree/bitcoin-protocol-and-ecosystem/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)*
- Evaluating a Bitcoin L2 or metaprotocol claim — a sidechain, a covenant proposal, an ordinals-based token scheme — against what the base layer actually guarantees versus what the L2 adds on top. — [source](https://llms-explorer.com/tree/bitcoin-protocol-and-ecosystem/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)*

## Project ideas

- Build a coin-selection algorithm that walks a wallet's UTXO set and picks inputs to minimize fees or consolidate dust, then compare it against a naive largest-first strategy. — [source](https://llms-explorer.com/tree/bitcoin-protocol-and-ecosystem/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)*
- Decode a raw Bitcoin transaction by hand or with a script to compute txid versus wtxid and confirm the weight and vbyte calculation that determines its fee. — [source](https://llms-explorer.com/tree/bitcoin-protocol-and-ecosystem/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)*
- Implement a minimal Lightning Network payment channel simulation — channel open, HTLC routing, cooperative close — to understand how BOLT-specified routing moves value off-chain. — [source](https://llms-explorer.com/tree/bitcoin-protocol-and-ecosystem/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)*
- Write a script that verifies a P2TR, Taproot, address's Merkle-path spend condition against a simple multisig script tree. — [source](https://llms-explorer.com/tree/bitcoin-protocol-and-ecosystem/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)*

## Antipatterns

- Treating a transaction with only a few confirmations as final settlement, when it can still be reorganized out of the chain, especially soon after being mined. — [source](https://llms-explorer.com/tree/bitcoin-protocol-and-ecosystem/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)*
- Broadcasting a transaction with too low a fee rate and no RBF signaling, leaving no way to bump the fee if it gets stuck during a mempool congestion spike. — [source](https://llms-explorer.com/tree/bitcoin-protocol-and-ecosystem/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)*
- Assuming every Bitcoin L2 offers the same security guarantees as the base layer — sidechains, drivechains, and shared-security schemes like Babylon each make different, non-identical trust assumptions. — [source](https://llms-explorer.com/tree/bitcoin-protocol-and-ecosystem/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)*
- Conflating the UTXO model with the account model when porting wallet or accounting logic from an Ethereum-style chain — a Bitcoin balance is the sum of unspent transaction outputs, not a single mutable balance field. — [source](https://llms-explorer.com/tree/bitcoin-protocol-and-ecosystem/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)*

## Known issues

- The halving schedule and 21M supply cap are protocol-enforced by the block-reward formula, but transaction fees, not the subsidy, are expected to become the dominant miner incentive as the subsidy continues to shrink. — [source](https://llms-explorer.com/tree/bitcoin-protocol-and-ecosystem/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)*
- Difficulty retargeting only adjusts every 2016 blocks, roughly two weeks, so a sudden large change in network hash rate can leave block times noticeably off-target until the next retarget. — [source](https://llms-explorer.com/tree/bitcoin-protocol-and-ecosystem/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)*
- Metaprotocols like ordinals, BRC-20, and Runes are built entirely on top of Bitcoin's base-layer data fields; the base protocol has no native concept of a token, so these schemes depend on off-chain indexers agreeing on interpretation rules. — [source](https://llms-explorer.com/tree/bitcoin-protocol-and-ecosystem/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)*
- Taproot, Schnorr, and MAST activated via soft fork, so older nodes that never upgraded still validate the chain but cannot independently verify the finer Taproot script semantics. — [source](https://llms-explorer.com/tree/bitcoin-protocol-and-ecosystem/) *(AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.)*

## Context files

- [Bitcoin protocol and ecosystem](https://llms-explorer.com/downloads/sources/mdb-context-hub/bitcoin-protocol-expert.md)
