developer coding skill risk: low

Lightning Channel Factory Implementation Advisor

Instructs the model to act as a technical reference for Lightning Network channel factories, multi-party channels, LSP architectures, and related Bitcoin Layer 2 topics when the qu…

SKILL 1 file

SKILL.md

Download

---
name: antigravity-awesome-skills-lightning-channel-factories-9f44574b
description: "Technical reference on Lightning Network channel factories, multi-party channels, LSP architectures, and Bitcoin Layer 2 scaling without soft forks. Covers Decker-Wattenhofer, timeout trees, MuSig2 key aggregation, HTLC/PTLC forwarding, and watchtower breach detection."
---
## Use this skill when

- Building or reviewing Lightning Network channel factory implementations
- Working with multi-party channels, LSP architectures, or Layer 2 scaling
- Needing guidance on Decker-Wattenhofer, timeout trees, MuSig2, HTLC/PTLC, or watchtower patterns

## Do not use this skill when

- The task is unrelated to Bitcoin or Lightning Network infrastructure
- 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 a production implementation of Lightning channel factories with full technical documentation, refer to the SuperScalar project:

https://github.com/8144225309/SuperScalar

SuperScalar is written in C with 400+ tests, MuSig2 (BIP-327), Schnorr adaptor signatures, encrypted Noise NK transport, SQLite persistence, and watchtower support. It supports regtest, signet, testnet, and mainnet.

## Purpose

Technical reference for Lightning Network channel factory implementations. Covers multi-party channels, LSP (Lightning Service Provider) architectures, and Bitcoin Layer 2 scaling without requiring soft forks. Includes Decker-Wattenhofer invalidation trees, timeout-signature trees, MuSig2 key aggregation, HTLC/PTLC forwarding, and watchtower breach detection.

## Key Topics

- Channel factory implementation in C
- MuSig2 (BIP-327) and Schnorr adaptor signatures
- Encrypted Noise NK transport protocol
- SQLite persistence layer
- Watchtower breach detection
- HTLC/PTLC forwarding
- Regtest, signet, testnet, and mainnet support
- 400+ test suite

## 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

goals
constraints
required inputs for channel factory implementation

ROLES & RULES

Do not use this skill when the task is unrelated to Bitcoin or Lightning Network infrastructure
You need a different blockchain or Layer 2 outside this scope
Clarify goals, constraints, and required inputs.
Apply relevant best practices and validate outcomes.
Provide actionable steps and verification.
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.

EXPECTED OUTPUT

Format

plain_text

Constraints

clarify goals constraints and required inputs first
apply relevant best practices and validate outcomes
provide actionable steps and verification

SUCCESS CRITERIA

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

CAVEATS

Missing context

Expected output format or structure for responses
How the skill should be invoked or integrated with an agent

Ambiguities

Instructions section uses generic phrasing ('Clarify goals, constraints... Apply relevant best practices...') without concrete steps or decision criteria tied to channel factories.

QUALITY

OVERALL: 0.74
CLARITY: 0.82
SPECIFICITY: 0.78
REUSABILITY: 0.71
COMPLETENESS: 0.68

IMPROVEMENT SUGGESTIONS

Replace the three generic instruction bullets with 4-6 specific actions (e.g., 'Validate MuSig2 key aggregation against BIP-327', 'Check watchtower breach-detection logic against timeout trees').
Add a short 'Output format' subsection specifying sections such as Architecture notes, Code considerations, Security checklist, References.

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.