bitcoin-proposals
Soft-fork proposals NOT activated on mainnet: CTV (BIP119), APO/APOAS (BIP118), OP_VAULT (BIP345), OP_CAT reactivation, drivechains (BIP300/301), spacechains, CISA. Status, mechanics, controversy per proposal. USE WHEN: discussing covenants, evaluating L2 design that depends on unactivated opcodes, understanding the soft-fork pipeline.
What this skill does
# Bitcoin Soft-Fork Proposals These are **not consensus-active on mainnet**. Some are deployed on signet (custom signets) or testnet for experimentation. Be explicit when reasoning: never present these as "Bitcoin" features without naming the proposal status. ## Covenants in general A covenant restricts how an output may be re-spent (where the funds go, in what shape, with what conditions). Existing scripts can restrict **who** spends; covenants restrict **how**. Use cases: - **Vaults** — cooldown period before final spend; recoverable from cold key. - **Congestion control** — pre-commit to a tree of payments. - **L2 protocols** — Ark, Spacechains, CoinPool depend on covenants. ## CTV — `OP_CHECKTEMPLATEVERIFY` (BIP119) ``` <TemplateHash> OP_CTV ``` Forces the tx to match a pre-committed template: - Output set, amount, scriptPubKeys. - Number of inputs (but NOT specific prevouts). - Locktime, sequence values. Template-hash is committed on-chain → spending tx must produce the exact set of outputs. **Status**: Proposed since 2020. Major debate around community split, no activation path. Active on **signet** for testing (specifically the "CTV signet"). **Use cases**: vaults, payment pools, congestion control, simple Ark variants. ## SIGHASH_ANYPREVOUT — APO / APOAS (BIP118) New SIGHASH flag. Sig commits to script + value but **not** to specific prevout txid:vout. ``` APO sighash (commits to scriptPubKey, not txid) APOAS sighash variant (also doesn't commit to script — even more permissive) ``` Original use case: **Eltoo** — Lightning channel update protocol that replaces commitment-tx penalty with simple state replacement. **Status**: Proposed. No active deployment yet. ## OP_VAULT (BIP345) Two-stage vault primitive: - `OP_VAULT` output: spend to a "trigger" path (begins cooldown) or recover path (immediate, to cold key). - After cooldown, spend the trigger to actual destination. Provides **first-class vault** semantics without complex script gymnastics. Works in P2TR script-path. **Status**: Draft / proposed. Some signet experimentation. ## OP_CAT reactivation Re-enable string concatenation in Tapscript. Disabled since 2010 genesis era (pulled due to DoS concerns, since obsoleted by stack-item size limits). Why people want it: - **Verifiable computation** — constructs proofs/scripts via concatenation. - **Quantum-resistant signature** schemes (Lamport / Winternitz one-time). - **BitVM2** — simplified bridge construction. - **Recursive covenants** with limited branching. **Status**: Proposed re-enabling in Tapscript only. No BIP number yet. ## Drivechains — BIP300 / BIP301 Sidechains pegged with miner-validated locks: - BIP300 — hashrate escrow with deposit/withdraw tx types. - BIP301 — blind merge mining. Allows trustless-of-miner-majority sidechains. Critique: trusts miners implicitly with all sidechain funds. **Status**: Proposed. Not deployed on mainnet. **LayerTwo Labs** runs testnet drivechain. ## Spacechains (Ruben Somsen) Sidechain idea using `OP_CAT` + `OP_CHECKSIGFROMSTACK` (also proposed) to enable arbitrary-script verification without explicit miner support. **Status**: Concept. Not a formal BIP. ## Cross-Input Signature Aggregation (CISA) Aggregate all signatures in a transaction into a single signature. Massive witness savings (n inputs → 1 sig instead of n sigs). Active research; not yet a deployable proposal. ## Status terminology | Status | Meaning | |--------|---------| | **Draft** | BIP author drafted, not yet broadly reviewed | | **Proposed** | Discussed, refined, awaiting deployment plan | | **Replaced** | Superseded by another BIP | | **Withdrawn** | Author withdrew | | **Active** | Consensus rule on mainnet | | **Final** | Specification frozen (e.g., BIP-32, format spec) | For consensus changes, "Active" requires a successful soft-fork deployment — never assume from "Proposed". ## Common pitfalls - Reasoning about a protocol that **depends** on CTV/APO/OP_CAT as if those were already active. Always name the dependency explicitly. - Citing drivechain TVL or activity → likely on a private testnet, not mainnet. - Confusing **signet** activation (custom signet challenge that includes the proposed opcode) with mainnet activation. ## See also - [consensus/SKILL.md](../consensus/SKILL.md) - [../../l2/drivechains-spacechains/SKILL.md](../../l2/drivechains-spacechains/SKILL.md) - [../../l2/ark/SKILL.md](../../l2/ark/SKILL.md) - [../../l2/bitvm/SKILL.md](../../l2/bitvm/SKILL.md)
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.