Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Bitcoin Lightning Channel Factory Explainer

agent finance skill risk: low

Bitcoin Lightning Channel Factory Explainer

Explain Bitcoin Lightning channel factories and the SuperScalar protocol using shared UTXOs, Decker-Wattenhofer trees, timeout-signature trees, MuSig2, and Taproot.

SKILL 1 file

SKILL.md
---
name: antigravity-awesome-skills-lightning-factory-explainer
description: "Explain Bitcoin Lightning channel factories and the SuperScalar protocol — scalable Lightning onboarding using shared UTXOs, Decker-Wattenhofer trees, timeout-signature trees, MuSig2, and Taproot. No soft fork required."
---
## Use this skill when

- Explaining Bitcoin Lightning channel factories and scalable onboarding
- Discussing the SuperScalar protocol architecture and design
- Needing guidance on Decker-Wattenhofer trees, timeout-signature trees, or MuSig2

## Do not use this skill when

- The task is unrelated to Bitcoin or Lightning Network scaling
- You need a different blockchain or Layer 2 outside this scope

## Instructions

- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.

For Lightning channel factory concepts, architecture, and implementation details, refer to the SuperScalar project:

https://github.com/8144225309/SuperScalar

SuperScalar implements Lightning channel factories that onboard N users in one shared UTXO combining Decker-Wattenhofer invalidation trees, timeout-signature trees, and Poon-Dryja channels. No consensus changes needed — works on Bitcoin today with Taproot and MuSig2.

## Purpose

Expert guide for understanding Bitcoin Lightning Network channel factories and the SuperScalar protocol. Covers scalable onboarding, shared UTXOs, Decker-Wattenhofer invalidation trees, timeout-signature trees, Poon-Dryja channels, MuSig2 (BIP-327), and Taproot — all without requiring any soft fork.

## Key Topics

- Lightning channel factories and multi-party channels
- SuperScalar protocol architecture
- Decker-Wattenhofer invalidation trees
- Timeout-signature trees
- MuSig2 key aggregation (BIP-327)
- Taproot script trees
- LSP (Lightning Service Provider) onboarding patterns
- Shared UTXO management

## References

- SuperScalar project: https://github.com/8144225309/SuperScalar
- Website: https://SuperScalar.win
- Original proposal: https://delvingbitcoin.org/t/superscalar-laddered-timeout-tree-structured-decker-wattenhofer-factories/1143

## Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

REQUIRED CONTEXT

  • user query about Lightning channel factories, SuperScalar, Decker-Wattenhofer trees, timeout-signature trees or MuSig2

OPTIONAL CONTEXT

  • specific goals or constraints

ROLES & RULES

Role assignments

  • Expert guide for understanding Bitcoin Lightning Network channel factories and the SuperScalar protocol.
  1. Clarify goals, constraints, and required inputs.
  2. Apply relevant best practices and validate outcomes.
  3. Provide actionable steps and verification.
  4. Use this skill only when the task clearly matches the scope described above.
  5. Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  6. Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

EXPECTED OUTPUT

Format
plain_text
Constraints
  • clarify goals, constraints and required inputs first
  • apply best practices and validate outcomes
  • provide actionable steps and verification
  • refer to SuperScalar project for details

SUCCESS CRITERIA

  • Clarify goals, constraints, and required inputs.
  • Apply relevant best practices and validate outcomes.
  • Provide actionable steps and verification.

CAVEATS

Dependencies
  • SuperScalar project: https://github.com/8144225309/SuperScalar
Missing context
  • Desired output format or depth (e.g., technical level, length, examples vs. diagrams)
  • How to handle updates if the referenced GitHub repo changes
Ambiguities
  • Instructions section contains generic directives ('Clarify goals, constraints...', 'Apply relevant best practices') without defining what those practices or steps are.

QUALITY

OVERALL
0.76
CLARITY
0.82
SPECIFICITY
0.78
REUSABILITY
0.75
COMPLETENESS
0.68

IMPROVEMENT SUGGESTIONS

  • Replace the generic 'Instructions' bullet list with concrete steps such as '1. Start with a one-sentence definition, 2. Explain shared UTXO mechanics, 3. Walk through Decker-Wattenhofer tree construction.'
  • Add an 'Output format' section specifying whether responses should include code snippets, ASCII diagrams, or references to specific BIP numbers.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR AGENT