lightning-loop-pool-lit
Lightning Labs liquidity tools: Loop (off-chain ↔ on-chain swaps), Pool (auction-based liquidity market), Lightning Terminal (Lit, web UI). Submarine swap mechanics behind Loop. USE WHEN: managing channel liquidity, evaluating Loop vs Boltz vs Peerswap, deploying Lit for fleet management.
What this skill does
# Lightning Loop / Pool / Terminal
Lightning Labs' suite of liquidity-management tools, built on top of
LND.
## Loop — submarine swaps
Loop lets you convert between on-chain and Lightning balance:
### Loop Out (LN → on-chain)
Use case: drain channels, reduce Lightning balance into on-chain.
```
LND ──── HTLC payment ────► Loop server
Loop server publishes on-chain HTLC
LND watches chain, receives on-chain payout via preimage reveal.
```
### Loop In (on-chain → LN)
Use case: inbound liquidity, rebalance.
```
LND publishes on-chain HTLC ────► Loop server
Loop server pays LND HTLC over LN
On-chain HTLC settled via preimage.
```
Loop = **submarine swap**. Atomic via shared preimage / HTLC scripts.
Fees: ~0.5% typically.
### loopd
```bash
loop in --amt 1000000 --htlc_conf_target 6
loop out --amt 5000000 --channel <chan-id>
loop monitor # watch ongoing swaps
```
## Pool — channel auction
Pool is a marketplace where:
- **Makers** (liquidity providers) commit liquidity for sale.
- **Takers** (channel-needers) bid for inbound.
Pool runs per-block batched auctions. Winning matches get a
dual-funded channel.
### poold
```bash
pool accounts new --amt 1000000 # deposit funds for bidding
pool orders submit ask --amt 500000 --duration 144 ... # offer to provide
pool orders submit bid --amt 1000000 --duration 144 ... # request liquidity
```
## Lightning Terminal (Lit)
Web UI bundling LND + Loop + Pool + Faraday + Taproot Assets daemon
+ Pool. Single web dashboard for node management.
```bash
litd # runs LND + sub-services + UI on port 8443
```
Web UI features:
- Balance, channels, payments tracker.
- Loop interface (one-click in/out).
- Pool interface (submit orders, view auctions).
- Taproot Assets management.
## Submarine swap protocol detail
Both Loop In and Loop Out use atomic swaps via HTLC:
### Loop Out flow
1. User generates preimage `P`, hash `H = SHA256(P)`.
2. User pays LN invoice with `H` to Loop server. HTLC route ends at
Loop server with `H`.
3. Loop server's HTLC has not yet been fulfilled by user (no `P`
revealed).
4. Loop server publishes on-chain HTLC at user's specified address,
spendable by user with `P`, refundable by Loop server after CLTV.
5. User claims on-chain output, revealing `P`.
6. Loop server uses `P` to fulfill the LN HTLC, gets paid.
Atomic: either both swap legs settle or neither (both refund).
## Alternatives
- **Boltz** — competing submarine swap service, also supports
Liquid swaps.
- **Peerswap** (CLN plugin, LND lncli plugin) — peer-to-peer swaps,
no third-party trust.
- **Splice-out** (CLN, ldk) — built-in; no third-party.
Lightning Loop has the broadest impl support; Peerswap is more
trust-minimized but requires both parties to support it.
## Common bugs
- Loop fails on swap due to mismatched fees: server's quote vs
current mempool fee → use higher `htlc_conf_target`.
- Stuck swap: user's LN HTLC sent but server's on-chain HTLC delayed
→ wait for CLTV refund or resubmit.
- Lit web UI requires LND macaroon; misconfigured → Auth failures.
## See also
- [submarine-swaps/SKILL.md](../submarine-swaps/SKILL.md)
- [lnd/SKILL.md](../lnd/SKILL.md)
- [../../l2/taproot-assets/SKILL.md](../../l2/taproot-assets/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.