What problem does it solve? Choosing what to build next in a large Lightning wallet codebase is hard: stalled branches, disabled UI, dead dispatch methods, and unverified novelty claims scatter across the repo. This Skill consolidates the maintainer-endorsed research directions, concrete file-level starting points, and the proof standards required before making any public claim about Zeus. ## Core Features & Use Cases - Four endorsed research directions: self-custodial UX parity (LSPS7, JIT channels, NWC background delivery), protocol leadership (BOLT12 offers, Cashu NUT-15, BIP-321), multi-backend robustness across 7 backends, and privacy leadership (Tor gaps, TLS defaults, stealth mode). - File-level entry points: each direction lists exact files, grep commands, and known issues such as the fenced LSPS7 refund UI in views/LSPS7/index.tsx and the unimplemented payLightningInvoiceStreaming dispatch. - Novelty claim governance: proof obligations for public claims including prior-art surveys, third-party reproducibility, verifiable builds, and the no-oversell rule tied to supports* capability gates. - Use Case: A contributor wants to pick up stalled work on the bip-321 branch. The Skill identifies the branch commit, the files it touches, and the concrete rebase-and-retest steps, plus which related skills govern storage or payment-path changes. ## Quick Start Ask the assistant to load the zeus-research-frontier skill and recommend which research direction or stalled thread to pick up next in the Zeus repository.
