All authors
Claude Skills by claude-dev-suite
github.com/claude-dev-suite739 skills119 installs1,909 views
- OrdinalsOrdinal theory: numbering scheme for individual satoshis (sat ordinals). ord client, sat-tracking, rare sat collecting, foundation for inscriptions / BRC-20 / sub-protocols. USE WHEN: working with ord client, tracking sats, building Ordinals apps.Votes: 0GitHub stars: 31
- RunesRunes: Casey Rodarmor's UTXO-native fungible token protocol. Activated at halving April 2024. Smaller on-chain footprint than BRC-20, native validation rules. USE WHEN: building Runes apps, comparing with BRC-20 / Atomicals.Votes: 0GitHub stars: 31
- Decentralized PoolsDecentralized mining pools: Public-Pool, BraiinsP2Pool, Solo CKPool, Datum (Ocean). Reduce centralization vs traditional pools. USE WHEN: solo mining, evaluating decentralized options, building censorship-resistant infrastructure.Votes: 0GitHub stars: 31
- DifficultyDifficulty adjustment algorithm: 2016-block re-target window, max 4x factor, time-warp considerations, real-world hashrate dynamics. USE WHEN: predicting next adjustment, understanding hashrate/ difficulty cycles, building mining analytics.Votes: 0GitHub stars: 31
- FirmwareASIC mining firmware: Braiins OS+, Vnish, BUMa, ESP-Miner/AxeOS (Bitaxe), stock firmware, custom firmware tradeoffs. Overclocking, undervolting, autotuning, efficiency curves. USE WHEN: deploying mining firmware, evaluating efficiency vs hashrate, choosing custom vs stock.Votes: 0GitHub stars: 31
- Pool ArchitecturesMining pool reward schemes: PPS, FPPS, PPLNS, PPS+, Score, prop. Block generation queue, share variance, payout cycles. Solo mining vs pooled. USE WHEN: comparing pools, designing reward systems, understanding miner economics.Votes: 0GitHub stars: 31
- PowBitcoin Proof of Work: SHA256d on block header, target, nonce iteration, hashrate, mining math. USE WHEN: explaining mining mechanics, debugging mining software, designing mining-related apps.Votes: 0GitHub stars: 31
- Stratum V1Stratum V1: TCP/JSON protocol between mining pool and miners. Subscribe, authorize, mining.notify, mining.submit. Most-used protocol but security/decentralization weaknesses. USE WHEN: integrating mining hardware, building pool / proxy software, debugging hash submission.Votes: 0GitHub stars: 31
- Stratum V2Stratum V2: encrypted, miner-driven mining protocol. Job Declaration, Template Provider, allows miners to choose their own tx set. Defeats pool-level censorship. USE WHEN: deploying SV2-capable mining infrastructure, evaluating V1 vs V2, integrating with Braiins Pool / Datum.Votes: 0GitHub stars: 31
- Atomic SwapsCross-chain atomic swaps: BTC ↔ LTC / BTC ↔ Liquid / BTC ↔ Monero via HTLC or adaptor signature schemes. Trustless swaps without centralized exchange. USE WHEN: building atomic swap services, evaluating cross-chain bridges, integrating with COMIT / submarine-swap variants.Votes: 0GitHub stars: 31
- Bip47 PaynymsBIP47 PayNyms — reusable payment codes via notification tx + Diffie-Hellman derivation. See also the wallet-side reference at ../../wallets/payment-codes/. USE WHEN: integrating PayNyms, evaluating against Silent Payments.Votes: 0GitHub stars: 31
- CoinjoinCoinJoin: collaborative tx where multiple users combine inputs to break common-input-ownership heuristic. Wabisabi (Wasabi 2.0), Whirlpool (Samourai), JoinMarket maker/taker. USE WHEN: implementing CoinJoin coordinator/client, evaluating privacy gain, designing post-CoinJoin hygiene.Votes: 0GitHub stars: 31
- DandelionDandelion++ (BIP156): tx broadcast privacy. Stem phase (forward to one peer) → fluff phase (gossip to all). Hides origin IP. USE WHEN: evaluating tx-broadcast privacy, implementing Dandelion- aware relay logic.Votes: 0GitHub stars: 31
- P2p ExchangesP2P KYC-free Bitcoin exchanges: Bisq (desktop, Tor), RoboSats (Tor / browser, Lightning), Hodl Hodl (web, multisig escrow). USE WHEN: evaluating KYC-free buy/sell options, integrating P2P trading.Votes: 0GitHub stars: 31
- PayjoinPayJoin (BIP78 + v2): receiver-augmented payment that breaks common-input-ownership heuristic. v2 adds async relay support. USE WHEN: implementing PayJoin sender/receiver, designing privacy- preserving payment flows, integrating with payjoin servers.Votes: 0GitHub stars: 31
- Silent PaymentsSilent Payments (BIP352): single static address from which sender derives unique output per payment. Schnorr-based blinding; no notification tx needed. USE WHEN: implementing BIP352 client/wallet, evaluating vs BIP47, understanding scan cost trade-offs.Votes: 0GitHub stars: 31
- StealthStealth addresses: ECDH-based derivation generating a unique output per payment. Pre-BIP47 / BIP352, conceptually similar. USE WHEN: understanding the family of stealth-address schemes, comparing with BIP47 / Silent Payments.Votes: 0GitHub stars: 31
- TorBitcoin over Tor: Tor v3 hidden services, onion-only nodes, bitcoind torcontrol integration, Lightning over Tor. USE WHEN: hardening node privacy, configuring onion-only setups, debugging Tor + bitcoind interaction.Votes: 0GitHub stars: 31
- BipsBitcoin Improvement Proposals index, organized by topic. Active soft forks, wallet standards, network protocol, format standards. Pointers to canonical text and historical context. USE WHEN: looking up a BIP number, citing a standard, or understanding the relationship between related BIPs.Votes: 0GitHub stars: 31
- ConsensusBitcoin consensus rules: block validation, transaction validation, soft-fork activation mechanics (BIP9, BIP8, Speedy Trial), nLockTime / nSequence semantics, mempool policy vs consensus distinction. USE WHEN: discussing what makes a tx/block valid, soft-fork deployment, reorg handling, "is this consensus-valid".Votes: 0GitHub stars: 31
- DescriptorsOutput descriptors: BIP380-385 family. Descriptor language for declaring scriptPubKey templates with key origin info, ranges, checksums. Functions: pkh, wpkh, sh, wsh, tr, multi, sortedmulti, multi_a, addr, raw, combo, rawtr. USE WHEN: importing watch-only wallets, defining multisig, declaring scan ranges, exchanging key info between wallets.Votes: 0GitHub stars: 31
- Message SigningGeneric Bitcoin message signing: BIP137 (legacy P2PKH-only) and BIP322 (modern, supports any output type). Used for proof-of-ownership, withdraw verification, federated authentication, exchange KYC-free attestation. USE WHEN: implementing "sign this message with your Bitcoin address", verifying ownership of an address, building auth via signing.Votes: 0GitHub stars: 31
- MiniscriptMiniscript: structured subset of Bitcoin Script with fragment types, satisfaction analysis, malleability resistance. Policy → Miniscript → Script compilation. Used in descriptors (wsh + tr) and modern wallets to express spending conditions safely. USE WHEN: composing complex spending conditions, deriving the cheapest satisfaction, ensuring scripts are non-malleable.Votes: 0GitHub stars: 31
- P2pBitcoin P2P network protocol: messages, version handshake, addr/addrv2, compact blocks (BIP152), compact block filters (BIP157/158), v2 transport encryption (BIP324), wtxid relay (BIP339), Erlay (BIP330), Dandelion++ (BIP156). USE WHEN: implementing/debugging a node, integrating with bitcoind P2P, understanding address gossip, designing privacy-preserving propagation.Votes: 0GitHub stars: 31
- Package RelayPackage relay and the mempool policy Bitcoin Core actually ships: opportunistic 1p1c relay, package validation, cluster limits, submitpackage RPC, package CPFP, sibling eviction with TRUC v3 (BIP431), P2A anchors (BIP433) and ephemeral dust. Critical for Lightning fee bumping and any multi-tx workflow. USE WHEN: implementing CPFP, designing fee-bump strategies, debugging "why won't my child confirm", reasoning about Lightning anchor pinning.Votes: 0GitHub stars: 31
- ProposalsSoft-fork proposals NOT activated on mainnet: consensus cleanup (BIP54), CTV (BIP119), the BIP448 rebindable-transaction bundle (BIP446/348/349), APO/APOAS (BIP118), OP_CHECKCONTRACTVERIFY (BIP443), OP_CAT (BIP347), the 2026 script/covenant BIP cluster (BIP440-443, 446, 448, 449), post-quantum proposals (BIP360/361), drivechains (BIP300/301), spacechains, CISA. Status, mechanics, controversy per proposal. USE WHEN: discussing covenants, evaluating L2 design that depends on unactivated opcodes...Votes: 0GitHub stars: 31
- PsbtPartially Signed Bitcoin Transaction format: BIP174 (v0), BIP370 (v2), BIP371 (Taproot fields). Roles (Creator, Updater, Signer, Combiner, Finalizer, Extractor), required fields per input/output type, Taproot-specific fields (tap_key_sig, tap_script_sig, tap_leaf_script, tap_bip32_derivation), magic bytes, separators. USE WHEN: building/signing/coordinating PSBTs, debugging "why won't my hardware wallet sign", cross-vendor multisig flows.Votes: 0GitHub stars: 31
- ScriptsBitcoin 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.Votes: 0GitHub stars: 31
- SegwitSegregated Witness: BIP141 (consensus), BIP143 (sighash), BIP144 (P2P serialization), BIP173 (Bech32 address). Witness segregation, weight units, txid vs wtxid, witness commitment. USE WHEN: working with native segwit (P2WPKH/P2WSH), embedded segwit (P2SH-P2WPKH/P2SH-P2WSH), or understanding the witness discount.Votes: 0GitHub stars: 31
- TaprootTaproot 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 taptree. USE WHEN: building/spending P2TR outputs, designing taptrees, reasoning about Schnorr-only contexts.Votes: 0GitHub stars: 31
- TransactionsBitcoin transaction structure: inputs, outputs, witness, version, locktime, serialization (legacy + segwit + wtxid), sighash modes, malleability, TRUC v3, ephemeral anchors. Quick-ref docs cover sighash combinatorics, serialization wire format, malleability classes, RBF/CPFP rules. USE WHEN: building/decoding transactions, choosing sighash flags, understanding txid vs wtxid, fee bumping logic.Votes: 0GitHub stars: 31
- Core Test FrameworkBitcoin Core's Python functional test framework: BitcoinTestFramework, TestNode, setup_network, sync_blocks, descriptors helpers, miniscript helpers. USE WHEN: writing tests against bitcoind, contributing to Bitcoin Core, testing custom mempool policies.Votes: 0GitHub stars: 31
- FuzzFuzz testing for Bitcoin code: Bitcoin Core's libFuzzer harnesses, rust-bitcoin / bdk / secp256k1 cargo-fuzz, AFL++. Seed corpus bootstrapping, regression tests. USE WHEN: hardening Bitcoin libraries, writing fuzz harnesses, reproducing fuzz-found crashes.Votes: 0GitHub stars: 31
- NigiriNigiri: regtest stack with Bitcoin + Esplora + electrs + Liquid + optional LN. CLI-based, fast iteration, includes faucet. USE WHEN: regtest with explorer dependency, full-stack E2E testing, dev environment with Esplora API.Votes: 0GitHub stars: 31
- PolarPolar: GUI for spinning up Lightning regtest networks. Supports LND, Core Lightning, Eclair, plus Lightning Terminal (litd) and Taproot Assets. Per-node config, payment simulation, channel topology editor, sim-ln activity, MCP server for AI agents. USE WHEN: building / testing Lightning apps, designing regtest channel topologies, demoing LN flows.Votes: 0GitHub stars: 31
- Property BasedProperty-based testing: proptest / quickcheck (Rust), hypothesis (Python). Strategies for tx serialization, descriptor round-trip, miniscript satisfaction. USE WHEN: testing Bitcoin parsers, ensuring round-trip invariants, catching edge cases beyond example tests.Votes: 0GitHub stars: 31
- RegtestRegtest mode: instant block generation, deterministic fork, multi-node setup, generatetoaddress, fallbackfee config. USE WHEN: building Bitcoin tests, simulating network conditions, scaffolding integration tests.Votes: 0GitHub stars: 31
- SignetSignet: signature-based testnet alternatives. Default signet, custom signets (signetchallenge), Mutinynet (30-sec blocks). Faster + more deterministic than testnet. USE WHEN: testing on a public-style network, avoiding mainnet fees but with realistic block timing.Votes: 0GitHub stars: 31
- BackupWallet backup formats: BIP39 mnemonic, SLIP-39 Shamir Backup, SeedQR, CompactSeedQR, Coldcard's CTL-format, paper backup hygiene, metal backup vendors and threat models. USE WHEN: designing backup UX, evaluating backup security, helping recover a backed-up seed.Votes: 0GitHub stars: 31
- Coin SelectionCoin selection algorithms: branch-and-bound (BnB), knapsack, single random draw (SRD), Murch's waste metric, change avoidance. Determines which UTXOs to spend for a given target. USE WHEN: implementing wallet send flow, choosing which UTXOs to consolidate, optimizing fees, designing privacy-preserving selection.Votes: 0GitHub stars: 31
- EntropyBIP85 deterministic entropy: derive child entropy/seeds from a parent BIP32 path. Used for sub-wallets, cross-app keys, deterministic randomness without separate backups. USE WHEN: spawning sub-wallets from one master seed, generating encryption keys deterministically, building a "memory" of one seed.Votes: 0GitHub stars: 31
- Fee EstimationFee estimation strategies: local mempool-based (estimatesmartfee), external APIs (mempool.space, BlockCypher), bitcoind's smart-fee algorithm, replacement bidding, fee-rate floor (incremental relay). USE WHEN: choosing a fee for a new tx, evaluating fee-bump amounts, designing fee policy for a service.Votes: 0GitHub stars: 31
- HdHD wallet implementation: BIP32 derivation, BIP39 mnemonic seed (with passphrase), BIP44/49/84/86 derivation paths, account structure, gap limit, watch-only via xpub, BIP352 silent payment scan/spend derivation and BIP392 sp() descriptors. USE WHEN: building/restoring an HD wallet, choosing derivation paths, debugging address generation, importing mnemonics.Votes: 0GitHub stars: 31
- LabelsBIP329 wallet labels portability: standard JSON Lines format for exporting/importing labels (addresses, txs, UTXOs, xpubs, inputs, outputs) across wallet software. USE WHEN: importing/exporting label sets, integrating with multiple wallets that should share annotations.Votes: 0GitHub stars: 31
- Payment CodesBIP47 reusable payment codes (PayNyms): notification transactions, derived per-counterparty addresses, Diffie-Hellman shared-secret derivation. Privacy-preserving alternative to address rotation. USE WHEN: implementing PayNyms / Sparrow / Samourai-compatible payment codes, evaluating BIP47 vs Silent Payments.Votes: 0GitHub stars: 31
- Rbf CpfpReplace-by-Fee (BIP125, full-RBF) and Child-Pays-For-Parent fee bumping. Cluster mempool policy (Core 31.0+), package CPFP via submitpackage, TRUC v3 (BIP431). Wallet-level fee bump strategies. USE WHEN: implementing fee bumping, debugging "stuck transaction", designing wallet UX for fee acceleration.Votes: 0GitHub stars: 31
- TimelocksBitcoin time-locks: nLockTime (BIP65 absolute), nSequence (BIP68/112 relative), CLTV/CSV opcodes, MTP rule (BIP113). Block-height vs unix-time, encoding rules. USE WHEN: building HTLCs, vaults, scheduled payments, escrow with cooldown, refund paths.Votes: 0GitHub stars: 31
- Uri SchemesBitcoin payment URI scheme (BIP21), Lightning URIs, BIP70/72 (mostly deprecated), PayJoin URI extension (BIP78), unified URIs combining on-chain + Lightning. USE WHEN: parsing/generating bitcoin: URIs, building QR codes, designing wallet payment requests.Votes: 0GitHub stars: 31
- VaultsBitcoin vault patterns: timelocked cooldown, hot/cold path with CSV, multisig vaults with quorum reduction over time, OP_VAULT proposal (BIP345), Revault architecture. USE WHEN: designing high-value custody, treasury setups, recovery schemes with publish-and-cooldown semantics.Votes: 0GitHub stars: 31
- CmakeCMake build system for C/C++ projects. Modern CMake (3.20+) with targets, properties, presets (CMakePresets.json), FetchContent, find_package, generator expressions, install rules, vcpkg/Conan integration. USE WHEN: user mentions "CMake", "CMakeLists.txt", "CMakePresets", "find_package", "FetchContent", "target_link_libraries", "vcpkg", "Conan", "C++ build" DO NOT USE FOR: Make, autotools, Bazel, Meson, Visual Studio .vcxproj direct editingVotes: 0GitHub stars: 31