lightning-consumer-wallets
Consumer Lightning wallet integration patterns: Phoenix, Breez SDK, Mutiny, Zeus, BlueWallet (LN), Aqua. Custodial vs non-custodial, LSP partnerships, mobile-specific UX (push notifications, background sync). USE WHEN: integrating with consumer wallets, designing self-custodial mobile UX, evaluating wallet SDK options.
What this skill does
# Consumer Lightning Wallets Most users access Lightning via mobile/desktop wallets. This skill catalogues major options and integration patterns. ## Wallet matrix (late 2025) | Wallet | Architecture | Custody | LSP | |--------|--------------|---------|-----| | **Phoenix** | Eclair core, mobile | Self-custodial via ACINQ trampoline | ACINQ exclusive | | **Breez SDK** | LDK or Greenlight under hood | Self-custodial | Multi (Breez choice) | | **Mutiny** | LDK web/mobile | Self-custodial | Multi (user choice) | | **Zeus** | LND/CLN/Embedded LND | Self-custodial; supports remote nodes | Configurable | | **BlueWallet (LN)** | LndHub backend | Custodial typically | LndHub provider | | **Aqua** | LDK + Liquid | Self-custodial multi-asset | Multi | | **Wallet of Satoshi** | Backend custodial | Custodial | n/a | | **Cash App** | LDK backend | Custodial | n/a | | **Strike** | Backend custodial | Custodial | n/a | | **Bitkit** | LDK | Self-custodial | Synonym (their LSP) | | **Alby** | Hybrid (NWC + custodial backend) | Custodial default; can connect own | n/a | ## Self-custodial mobile patterns ### Phoenix - ACINQ runs an Eclair node as the user's "trampoline". - User wallet talks to ACINQ via custom protocol. - ACINQ never holds user keys; can refuse to forward but can't steal. - Channels open dynamically as needed (splice-on-demand). - Backups: 12-word seed + automatic encrypted state to ACINQ cloud. ### Breez SDK - Open-source SDK (Apache 2.0). - Can use Greenlight (CLN) or LDK as backend. - Multi-language bindings: Swift, Kotlin, Rust, Dart, JS, Python. - Useful for app integrators wanting plug-and-play LN. ### Mutiny Wallet - Web wallet (browser tab) + mobile app. - Pure LDK in WebAssembly for browser version. - Multi-LSP: rotate, choose, fallback. - Encrypted state to user-supplied cloud (VSS). ### Zeus - "Power user" wallet — connects to user's own LND/CLN/Embedded LND node. - For Embedded mode: ships LND-mobile, runs locally. - For Remote: connect via macaroon + Tor / clearnet. - Most flexible; not as plug-and-play. ## Mobile UX challenges ### Always-online problem LN nodes need to be online to: - Watch for HTLCs. - Respond to channel updates. - Detect cheating. Mobile devices: NOT always online. Solutions: - **Watchtowers**: outsource monitoring. - **Hosted node** (Greenlight, custodial): always-online server with signing on device. - **Trampoline + LSP** (Phoenix model): node-like service with user keys. - **Background sync**: app wakes periodically (iOS/Android limits). - **Push notifications**: peer notifies on important events (some LSPs offer this). ### Push notification flow LSP has user's mobile push token. When channel event needs response: - LSP sends silent push. - Mobile wakes, opens connection to LSP. - Handles event. Requires careful coordination (Apple/Google background limits). ## Integration patterns ### Build a custodial backend - Run LND/CLN backend. - Create user accounts; track balances. - Generate invoices on demand. - Forward HTLC payments via your node. ### Build a self-custodial mobile app - **Best**: Breez SDK or LDK Node (hides complexity). - **More control**: directly use LDK Rust crates. - Provide LSP integration for inbound liquidity. ### Build a Lightning Address resolver - HTTP server with `/.well-known/lnurlp/<user>` endpoint. - Backend talks to your LN node (LND/CLN/phoenixd/LDK). - See [lightning-address/SKILL.md](../lightning-address/SKILL.md). ## Wallet SDK comparison | SDK | Backends | Bindings | Self-custody | |-----|----------|----------|--------------| | **Breez SDK** | LDK + Greenlight | many | yes | | **LDK Node** | LDK | Rust + bindings | yes | | **Lightning Toolkit / Bitkit SDK** | LDK | native | yes | | **LndHub** | LND | REST | no (custodial) | | **Greenlight Client** | CLN cloud | many | yes | For new mobile app integrations as of 2025, **Breez SDK** or **LDK Node** are the top choices. ## Common bugs - Treating LSP as fully trusted → didn't run watchtower → potentially vulnerable. - Bg-sync misconfigured → channels close due to inactivity. - iOS background restrictions ignored → app killed before processing channel events. - Custodial backend with no insolvency monitoring → outage = users funds locked. ## See also - [lsp/SKILL.md](../lsp/SKILL.md) - [ldk/SKILL.md](../ldk/SKILL.md) - [phoenixd/SKILL.md](../phoenixd/SKILL.md) - [greenlight/SKILL.md](../greenlight/SKILL.md) - [watchtowers/SKILL.md](../watchtowers/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.