bitcoin-scripts
/bitcoin-scripts
Bitcoin Script language: stack execution model, opcodes, all output types (P2PK, P2PKH, P2SH, P2WPKH, P2WSH, P2TR, P2A, Tapscript), witness construction, sig encoding (DER/Schnorr). Quick refs: opcode reference, output-type construction, Tapscript diff vs legacy. USE WHEN: writing/decoding scriptPubKey, building scriptSig/witness, understanding "what does this script do", reading raw txs.
- Author
- claude-dev-suite ↗
- Repository
- claude-dev-suite ↗
- Licence
- MIT
- Last repository change
- 21.10.2026
Assessment and security
- Files in this package
- 4
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 21.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Bitcoin Script language: stack execution model, opcodes, all output types (P2PK, P2PKH, P2SH, P2WPKH, P2WSH, P2TR, P2A, Tapscript), witness construction, sig encoding (DER/Schnorr). Quick refs: opcode reference, output-type construction, Tapscript diff vs legacy. USE WHEN: writing/decoding scriptPubKey, building scriptSig/witness, understanding "what does this script do", reading raw txs.
Triggers from the description
Original author description
Bitcoin Script language: stack execution model, opcodes, all output types (P2PK, P2PKH, P2SH, P2WPKH, P2WSH, P2TR, P2A, Tapscript), witness construction, sig encoding (DER/Schnorr). Quick refs: opcode reference, output-type construction, Tapscript diff vs legacy. USE WHEN: writing/decoding scriptPubKey, building scriptSig/witness, understanding "what does this script do", reading raw txs.
How it works
- Execution model
- Output type catalogue
- Sig encoding
- Witness construction (SegWit v0)
- Witness construction (Taproot)
- Standardness
- See also
SKILL.md preview
--- name: bitcoin-scripts description: | Bitcoin Script language: stack execution model, opcodes, all output types (P2PK, P2PKH, P2SH, P2WPKH, P2WSH, P2TR, P2A, Tapscript), witness construction, sig encoding (DER/Schnorr). Quick refs: opcode reference, output-type construction, Tapscript diff vs legacy. USE WHEN: writing/decoding scriptPubKey, building scriptSig/witness, understanding "what does this script do", reading raw txs. allowed-tools: Read, Grep, Glob --- # Bitcoin Script > **Quick refs**: [opcodes.md](quick-ref/opcodes.md), [output-types.md](quick-ref/output-types.md), [tapscript.md](quick-ref/tapscript.md) Bitcoin Script is a **stack-based**, **non-Turing-complete** (no loops), forth-like language. Each opcode pushes/pops bytes from a stack. Validity = stack contains a single non-zero element after execution. ## Execution model 1. Initialize empty stack. 2. Concatenate `scriptSig + scriptPubKey` (legacy) — execute serialized. *(Disabled post-BIP16 P2SH for the segwit/taproot path.)* 3. (For SegWit/Taproot) Witness stack pushes are pre-loaded onto the stack, then `scriptPubKey` (or witness script) executes. 4. After execution: top of stack must be non-zero / true. ## Output type catalogue | Type | scriptPubKey | Address | |------|--------------|---------| | **P2PK** | `<33 or 65-byte pubkey> OP_CHECKSIG` | none (uses P2PKH addr) | | **P2PKH** | `OP_DUP OP_HASH160 <20-byte hash> OP_EQUALVERIFY OP_CHECKSIG` | `1...` (Base58) | | **P2SH** | `OP_HASH160 <20-byte hash> OP_EQUAL` | `3...` (Base58) | | **P2WPKH** (v0) | `OP_0 <20-byte hash>` | `bc1q...` (Bech32) | | **P2WSH** (v0) | `OP_0 <32-byte hash>` | `bc1q...` (Bech32) | | **P2TR** (v1) | `OP_1 <32-byte tweaked x-only pubkey>` | `bc1p...` (Bech32m) | | **P2A** (v1, not Taproot) | `OP_1 <0x4e73>` (4 bytes total) | `bc1pfeessrawgf` (Bech32m) | P2PK, P2PKH = pre-2012 patterns, still consensus-valid. Mainnet wallets should use SegWit v0 (P2WPKH/P2WSH) as default and Taproot (P2TR) where feasible. **Parsing trap**: witness v1 does not imply Taproot. Pay-to-Anchor (P2A, BIP433 — Draft, assigned 2025-12-08) is a witness v1 output whose program is only **2 bytes** (`0x4e73`, "fees" in Bech32m). Dispatch on program length, not on witness version, or a decoder will mis-read a P2A output as a malformed P2TR. P2A is keyless — spending needs no signature and, to be standard, no witness data at all — and exists as a CPFP fee-bump hook for pre-signed L2 transactions. Spending P2A inputs became standard in Bitcoin Core 28.0 (October 2024); creating such outputs was already standard. ## Sig encoding - **ECDSA** (legacy/segwit v0): DER-encoded signature + 1-byte sighash flag suffix (`<r,s>` low-s only since BIP146). - **Schnorr** (Taproot): 64-byte raw signature. Optional 1-byte sighash if not `SIGHASH_DEFAULT` (0x00) → 65 bytes. ## Witness construction (SegWit v0) For P2WPKH spending: ``` witness: <signature DER + sighash byte> <pubkey 33 bytes> ``` For P2WSH spending: ``` witness: <stack items consumed by witnessScript> ... <witnessScript bytes> ← last element, hashed for verification ``` ## Witness construction (Taproot) Two paths: - **Key path** (default, cheapest, indistinguishable from single-sig): ``` witness: [<schnorr sig>] ``` - **Script path**: ``` witness: [<args for leaf script> ... <leaf script> <control block>] ``` Control block: `0xc0 | parity` + internal pubkey (32) + merkle path. ## Standardness Mempool policy enforces: - `OP_RETURN` (nulldata): `-datacarriersize` caps the aggregate `scriptPubKey` bytes across *all* nulldata outputs in the tx, and multiple such outputs are allowed. Default 100,000 since Bitcoin Core 30.0 (2025-10-10) — effectively uncapped, the 400k-weight standard tx limit binds first. `-datacarriersize=83` restores the old 80-byte-payload limit, but as an aggregate only — Core has no per-output count check; Bitcoin Knots still defaults to 83 and to a single nulldata output (checked September 2026). - No multi-sig with > 3 keys via "bare" multisig (post-P2SH only). - No non-canonical signatures (low-s, DER strict). - Tapscript opcodes: `OP_CHECKSIGADD` is consensus-active; new opcodes added per leaf-version policy. ## See also - [taproot/SKILL.md](../taproot/SKILL.md) - [miniscript/SKILL.md](../miniscript/SKILL.md) — script policy compiler - [descriptors/SKILL.md](../descriptors/SKILL.md)
Files in this package (4)
- SKILL.md 4 KB
- quick-ref/opcodes.md 4 KB
- quick-ref/output-types.md 4 KB
- quick-ref/tapscript.md 3 KB
Versions
The database has no other skills named bitcoin-scripts.
Database snapshot: 13.11.2026 · package version 39dc1ffd15a8 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95bitcoin-taproot
Taproot soft fork: BIP340 (Schnorr signatures), BIP341 (key tweak + script-path), BIP342 (Tapscript). x-only pubkeys, key-path vs script-path spending, control block, leaf versions, taptweak math. Quick refs: tweak math, control block layout, sighash differences, building a… - 95bitcoin-schnorr
BIP340 Schnorr signatures over secp256k1: sign/verify, x-only pubkeys, tagged hashes, batch verification, key tweaking. Building block for Taproot, MuSig2, FROST, adaptor signatures, DLCs. Quick refs: signing pseudocode, batch verification, common mistakes. USE WHEN:… - 95blockchain-bitcoin
Use this skill when asked about Bitcoin internals, Bitcoin Core, Bitcoin Script, Taproot, mining, Proof of Work, Lightning Network, BIP standards, Ordinals, BRC-20, Runes, Bitcoin L2s (Stacks, RSK, Babylon), and Bitcoin protocol development. Languages: C++, Rust, Python,…