How do I install the Lightning Factory Explainer skill?

Run npx skillmds@latest add francostino/lightning-factory-explainer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Lightning Factory Explainer safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Lightning Factory Explainer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Lightning Factory Explainer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Lightning Factory Explainer?

FrancoStino (@francostino) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Lightning Factory Explainer by francostino

Name: Lightning Factory Explainer
Rating: 4.2 (5 reviews)
Author: FrancoStino

Lightning Factory Explainer

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.

FrancoStino Updated Sep 8, 2026 63 repo stars

File contents

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

Example

User request:

Explain Bitcoin Lightning channel factories and scalable onboarding.

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.

---name: lightning-factory-explainerdescription: 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/SuperScalarSuperScalar 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.## PurposeExpert 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## Example**User request:**> Explain Bitcoin Lightning channel factories and scalable onboarding.## 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.

Frequently asked questions