All authors
Claude Skills by claude-dev-suite
github.com/claude-dev-suite739 skills119 installs1,909 views
- Embitembit: Python Bitcoin library designed for embedded / hardware wallets (MicroPython compatible). Used by Specter DIY, Krux, SeedSigner. USE WHEN: building HW signers, MicroPython Bitcoin apps, low-resource Python.Votes: 0GitHub stars: 31
- Hdwallet Pyhdwallet (Python): HD wallet generator + key derivation. Multi-coin, BIP32/39/44/49/84/86/141. USE WHEN: deriving keys for many cryptocurrencies, scripting key generation in Python.Votes: 0GitHub stars: 31
- LdkLightning Dev Kit (LDK): modular Rust crates for embedding Lightning in apps. ldk-node for opinionated quick-start. Bindings to Swift / Kotlin / Python. USE WHEN: embedding Lightning in mobile/desktop apps, building custom LN logic.Votes: 0GitHub stars: 31
- Libbitcoinlibbitcoin: comprehensive C++ Bitcoin library. Multiple toolkits (libbitcoin-system, libbitcoin-server, libbitcoin-explorer). Alternative implementation focused on cleanliness. USE WHEN: studying alternative Bitcoin codebases, building C++ Bitcoin services.Votes: 0GitHub stars: 31
- Libwallylibwally-core: Blockstream's C library for wallet primitives. BIP32/39, PSBT, Liquid Confidential Transactions, BIP143, Schnorr. Bindings to Python, JS, Java, Swift. USE WHEN: building cross-language wallets via libwally bindings, integrating Liquid CT.Votes: 0GitHub stars: 31
- Lnd Golnd Go libraries: lnrpc (gRPC client), chantools (channel utilities), loopd (Loop client), poold (Pool client), neutrino (BIP157/158 SPV). USE WHEN: building Go apps integrating with LND, Loop, or running Neutrino light clients.Votes: 0GitHub stars: 31
- Mempool Jsmempool.js (@mempool/mempool.js): TypeScript client for mempool.space API. REST + WebSocket; address history, fee estimates, mining stats. USE WHEN: integrating mempool.space data, building wallets / explorers.Votes: 0GitHub stars: 31
- Miniscript Rsrust-miniscript: Rust crate for Miniscript and descriptor handling. Policy compilation, satisfaction analysis, descriptor parsing for legacy + Tapscript. USE WHEN: working with descriptors / miniscript in Rust, building wallets that compose spending conditions.Votes: 0GitHub stars: 31
- NbitcoinNBitcoin: comprehensive .NET / C# Bitcoin library. Used by BTCPay Server, NBXplorer, many .NET tools. Tx, Script, PSBT, BIP32, HW wallet integration. USE WHEN: building .NET Bitcoin apps, integrating with BTCPay ecosystem.Votes: 0GitHub stars: 31
- Python Bitcoinlibpython-bitcoinlib by Peter Todd: low-level Bitcoin primitives in Python. Tx, Script, Address, key types, RPC client. USE WHEN: scripting Bitcoin operations in Python, low-level manipulation, Bitcoin Core RPC integration.Votes: 0GitHub stars: 31
- Rust Bitcoinrust-bitcoin: Rust crate for Bitcoin primitives. Tx, Block, Script, Address, Network, key types, PSBT, BIP32. Foundation for BDK, LDK, miniscript-rs. USE WHEN: building Bitcoin apps in Rust, parsing/constructing txs, working with addresses + scripts.Votes: 0GitHub stars: 31
- Rust Dlcrust-dlc: Rust DLC implementation. Funding, CET construction, oracle attestation handling, refund logic. USE WHEN: building DLC apps in Rust, integrating oracle-driven Bitcoin contracts.Votes: 0GitHub stars: 31
- Scure Btc Signer@scure/btc-signer: modern audited Bitcoin signer in TypeScript. Pure functional, minimal dependencies, browser-friendly. USE WHEN: building modern web/mobile Bitcoin apps, evaluating bitcoinjs-lib alternative.Votes: 0GitHub stars: 31
- Secp256k1 Clibsecp256k1: the canonical secp256k1 C library. Used by Bitcoin Core, rust-secp256k1, all major language bindings. USE WHEN: low-level crypto in C/C++, building bindings, performance- critical paths.Votes: 0GitHub stars: 31
- Secp256k1 Rsrust-secp256k1: Rust bindings to libsecp256k1 (C). ECDSA, Schnorr, ECDH, key tweaking, MuSig2 (BIP327, since 0.33). USE WHEN: low-level crypto in Rust, working with raw secp256k1 operations.Votes: 0GitHub stars: 31
- Tapd Gotaproot-assets daemon (tapd): Go implementation of Taproot Assets Protocol by Lightning Labs. Companion to LND. USE WHEN: integrating with tapd, building Taproot Assets apps in Go.Votes: 0GitHub stars: 31
- Amp MppMulti-Path Payments (MPP) — split a payment across multiple parallel routes; same payment hash, payment_secret binds parts. AMP (Atomic Multipath) — variant where each part has different hash; receiver derives shared secret. USE WHEN: implementing payment splitting, debugging "couldn't route full amount", evaluating MPP vs AMP.Votes: 0GitHub stars: 31
- Bolt12BOLT12 offers: reusable invoices, blinded paths, recurring payments, multi-asset (Taproot Assets layered). Replaces BOLT11 for many use cases. USE WHEN: implementing/integrating offers, designing recurring payments, evaluating BOLT11 vs BOLT12 trade-offs.Votes: 0GitHub stars: 31
- BoltsBOLT (Basis of Lightning Technology) specification index. Wire format, channel management, onion routing, gossip, invoices, feature bits. Quick refs: BOLT-by-BOLT summary, message-type tables, feature-bit registry. USE WHEN: implementing/reading Lightning protocol, looking up message types, debugging interop between implementations.Votes: 0GitHub stars: 31
- Channel JammingChannel jamming attacks: slow-jam (long-held HTLCs exhaust slots), fast-jam (rapid hold/release exhausts liquidity). Mitigations: upfront fees, reputation, hold-fee proposals. USE WHEN: assessing LN security model, designing reputation systems, evaluating jamming-resistant routing.Votes: 0GitHub stars: 31
- ChannelsLightning channel mechanics: funding tx, commitment tx, anchor outputs, zero-fee commitments (v3/TRUC), to_local / to_remote outputs, dual-funded (v2), zero-conf, wumbo, taproot channels, splicing. Quick refs: state machine, commitment tx structure, force-close flow. USE WHEN: opening/closing channels, debugging force-closes, designing channel UX, evaluating anchor vs static-remote-key tradeoffs.Votes: 0GitHub stars: 31
- ClnCore Lightning (CLN, formerly c-lightning) by Blockstream: lightningd, lightning-cli, plugin architecture (Python pyln-client, Rust cln-plugin, Go glightning), commando, BOLT12 leadership, xpay/askrene payments. USE WHEN: integrating with CLN, writing plugins, debugging CLN-specific behaviour, leveraging BOLT12 features, migrating payments from pay to xpay.Votes: 0GitHub stars: 31
- Consumer WalletsConsumer Lightning wallet integration patterns: Phoenix, Breez SDK, Zeus, BlueWallet (LN), Aqua, Bitkit. Custodial vs non-custodial, LSP partnerships, mobile-specific UX (push notifications, background sync). USE WHEN: integrating with consumer wallets, designing self-custodial mobile UX, evaluating wallet SDK options.Votes: 0GitHub stars: 31
- EclairEclair Lightning implementation by ACINQ: Scala/Akka, eclair-cli, plugin system, primarily backend service. Powers Phoenix wallet's server side and ACINQ's main routing node. USE WHEN: deploying Eclair as backend, integrating with ACINQ's Phoenix backend, evaluating Scala/JVM Lightning options.Votes: 0GitHub stars: 31
- GossipBOLT 7 gossip: node_announcement, channel_announcement, channel_update. Sync via gossip_queries, channel range queries, gossip rate limiting, pruning stale announcements. USE WHEN: implementing/debugging gossip sync, managing graph storage, designing rate limits.Votes: 0GitHub stars: 31
- GreenlightGreenlight by Blockstream: hosted CLN with self-custodial signing. Server runs the full CLN node; user retains private keys via signer protocol. Mobile-friendly without running a full LN node. USE WHEN: building mobile/web LN apps with self-custody but no on-device daemon, integrating with Blockstream's hosted infra.Votes: 0GitHub stars: 31
- HtlcsHTLC (Hash Time-Locked Contract) lifecycle: offered/received, fulfill via preimage, fail/timeout, 2nd-stage txs. Modern variant PTLCs (Point Time-Locked Contracts) with adaptor signatures. USE WHEN: implementing payment forwarding, debugging stuck HTLCs, reasoning about CLTV deltas in routes.Votes: 0GitHub stars: 31
- KeysendKeysend / spontaneous payments: send Lightning to a destination without an invoice. Receiver derives preimage from sender-supplied TLV record. BOLT 9 bit 50. USE WHEN: implementing tipping flows, designing zero-friction micro-payments, evaluating keysend vs BOLT11 invoice flow.Votes: 0GitHub stars: 31
- LdkLDK (Lightning Dev Kit): modular Rust crates for building custom Lightning apps. ldk-node for opinionated quick-start. ChannelManager, ChainMonitor, Router, async signer, persistence. USE WHEN: embedding Lightning into mobile/desktop apps, building custom Lightning logic, scaling beyond LND-style daemon.Votes: 0GitHub stars: 31
- Lightning AddressLightning Address (LUD-16): email-style identifier resolving to LNURL-pay endpoint. user@domain.com → /.well-known/lnurlp/user. Also covers BIP 353 DNS payment instructions (₿user@domain, DNSSEC TXT record) and bLIP-32 onion-message DNS resolution. USE WHEN: building/registering Lightning Addresses or BIP 353 names, designing resolver / payer wallet logic.Votes: 0GitHub stars: 31
- LndLND (Lightning Network Daemon) by Lightning Labs: gRPC + REST API, macaroons, lncli, autopilot, channel backups (SCB), Tor support, watchtowers, integration with bitcoind/btcd/Neutrino backend. USE WHEN: integrating with LND, scripting lncli, debugging LND-specific issues, designing LND-based services.Votes: 0GitHub stars: 31
- LnurlLNURL: bech32-encoded HTTP URL fetched by wallet to enable payment flows. LUDs (LNURL specs): LUD-01 (encoding), LUD-04 (auth), LUD-06 (pay), LUD-09 (success action), LUD-12 (comment), LUD-16 (lightning address), LUD-21 (verify). USE WHEN: implementing LNURL servers/clients, building Lightning Address resolver, designing pay/withdraw/auth flows.Votes: 0GitHub stars: 31
- Loop Pool LitLightning Labs liquidity tools: Loop (off-chain ↔ on-chain swaps), Pool (auction-based liquidity market), Lightning Terminal (Lit, web UI). Submarine swap mechanics behind Loop. As of September 2026 Loop is the live general-purpose option: Boltz swaps are offline (suspended 2026-08-03) and Peerswap rejects new L-BTC swaps (v7.0.1, 2026-09-07). USE WHEN: managing channel liquidity, evaluating Loop vs Boltz vs Peerswap, deploying Lit for fleet management.Votes: 0GitHub stars: 31
- LspLSP (Lightning Service Provider) specifications: BLIPs, JIT channels, on-pay channel open, MPP-trampoline, BOLT12 hosted invoice. Major LSPs: ACINQ (Phoenix backend), Olympus by ZEUS, Megalith, Flashsats, Magma. USE WHEN: integrating with an LSP, designing LSP services, evaluating LSP options for a wallet.Votes: 0GitHub stars: 31
- NwcNostr Wallet Connect (NWC, NIP-47): wallet remote control via Nostr relays. App on one device drives wallet on another via signed JSON messages over Nostr. USE WHEN: integrating wallet-side or app-side NWC, designing remote-control flows, evaluating NWC vs WebLN.Votes: 0GitHub stars: 31
- OnionSphinx onion routing for Lightning (BOLT 4): packet structure, per-hop encryption, payload TLV, blinded paths, attribution data, onion messages. USE WHEN: implementing onion construction/decryption, debugging routing payloads, designing onion-based off-chain protocols.Votes: 0GitHub stars: 31
- PhoenixdPhoenixd by ACINQ: headless server build of Phoenix wallet for self-hosting. Single-node Lightning daemon with batteries-included ACINQ swap-in / swap-out, BOLT12 receive, WebSocket payments API. USE WHEN: deploying a self-hosted minimal Lightning daemon for a service (point-of-sale, donation page, micro-merchant), avoiding full LND/CLN complexity.Votes: 0GitHub stars: 31
- Pinning AttacksPinning attacks: low-fee descendant txs block honest fee-bumping by exploiting mempool descendant policy. Anchor outputs (BOLT-3), TRUC v3 (BIP431), P2A + ephemeral dust, and the single shared anchor of `zero_fee_commitments` as defenses. USE WHEN: auditing fee-bump robustness, evaluating channel security, reviewing post-2024 LN deployments.Votes: 0GitHub stars: 31
- Replacement CyclingReplacement cycling attack on Lightning (Riard 2023): exploits BIP125 rule 5 to indefinitely delay an honest HTLC-timeout, costing the victim. Mitigated by TRUC v3 + ephemeral anchors. USE WHEN: auditing LN security posture, evaluating fee-bumping strategies, understanding why TRUC was activated.Votes: 0GitHub stars: 31
- RoutingLightning pathfinding and routing: cost models, MPP / AMP / trampoline, blinded paths (BOLT 4 update), apriori probability, pickhardt-payments. USE WHEN: implementing/tuning a routing algorithm, debugging "no route" errors, evaluating pathfinding strategies.Votes: 0GitHub stars: 31
- SplicingChannel splicing: splice-in (adding capacity) and splice-out (withdrawing) without closing the channel. Replaces "close and reopen" with one splice tx. USE WHEN: increasing/decreasing channel capacity in production, designing dynamic-balance LSP integrations, planning channel lifecycle.Votes: 0GitHub stars: 31
- Submarine SwapsSubmarine swaps: atomic on-chain ↔ Lightning conversions via shared HTLC preimage. Boltz protocol, Loop protocol, Peerswap (P2P), trustless variants with adaptor signatures. Boltz swaps are offline (suspended 2026-08-03); Loop, Peerswap and Blockstream Swaps (beta) are the live options as of September 2026. USE WHEN: building swap services, integrating with Loop / Peerswap / Blockstream Swaps, reading Boltz as a protocol reference, designing trust-minimized swap flows.Votes: 0GitHub stars: 31
- Taproot ChannelsSimple Taproot Channels (feature bits 80/81): MuSig2-aggregated funding output, Tapscript commitment leaves, taproot-native HTLCs. USE WHEN: enabling taproot channels in your impl, evaluating cooperative-spend privacy gains, designing taproot HTLC scripts.Votes: 0GitHub stars: 31
- TrampolineTrampoline routing: outsource pathfinding to "trampoline" nodes for clients that lack full graph knowledge. Mobile-friendly. Eclair (ACINQ/Phoenix) is the reference deployment; LDK receives and forwards; still unmerged as BOLTs PR #836 (September 2026). USE WHEN: implementing trampoline-aware sender/receiver, evaluating trampoline vs full pathfinding.Votes: 0GitHub stars: 31
- UmaUMA (Universal Money Address): Lightspark's spec extending Lightning Address with non-USD currencies, KYC compliance, sender attestation, multi-currency exchange via Lightning routing. USE WHEN: integrating with UMA-enabled providers (mostly enterprise), building cross-currency LN payment flows.Votes: 0GitHub stars: 31
- WatchtowersWatchtower architecture: encrypted breach blob storage, justice transactions, monitoring outsourced for offline channels. LN-Symmetry (eltoo, BIP 448) alternatives. USE WHEN: deploying a watchtower service, evaluating watchtower vendors, designing self-hosted monitoring.Votes: 0GitHub stars: 31
- WeblnWebLN: browser API for Lightning. window.webln exposed by wallet extensions / mobile webviews. Methods: enable, getInfo, sendPayment, makeInvoice, signMessage. Bitcoin Connect (modern wrapper). USE WHEN: building web apps with Lightning payments, integrating with Alby/getalby, designing WebLN-compatible flows.Votes: 0GitHub stars: 31
- AtomicalsAtomicals protocol: alternative metaprotocol family with ARC-20 (fungible) and AVM (Atomicals VM) for richer logic. UTXO-bound digital objects. USE WHEN: working with Atomicals, comparing with Ordinals / Runes.Votes: 0GitHub stars: 31
- Brc 20BRC-20: fungible token standard via JSON inscriptions. Deploy / mint / transfer operations. Permissionless and unaudited; large ecosystem post-2023. USE WHEN: building BRC-20 tooling, evaluating token issuance on Bitcoin, comparing with Runes / Taproot Assets.Votes: 0GitHub stars: 31
- InscriptionsInscriptions: arbitrary data committed to specific sats via Taproot envelope structure. Foundation for BRC-20, recursive inscriptions, "Bitcoin NFTs". USE WHEN: creating/parsing inscriptions, debugging inscription flow, evaluating inscription cost / fee impact.Votes: 0GitHub stars: 31