zeus-lightning-reference

Zeus uses a hand-rolled decoder in utils/Bolt11Utils.ts with an LRU cache of 256 entries and lazy self-replacing getters for destination and signature fields. The lazy getters defer expensive secp256k1 public-key recovery until first access, so you must never spread or JSON.stringify a decoded invoice.

MPP splits one payment across multiple routes, while AMP is LND's atomic variant that also works without an invoice. In Zeus, MPP requires LND v0.10.0+ and AMP requires v0.13.0+, and AMP is forced on when invoice feature bit 30 is required.

ZEUS Pay uses the Zaplocker hodl-invoice scheme: the phone pre-generates 250 preimages and submits their hashes to zeuspay.com, which holds incoming HTLCs. When the app comes online, it redeems by creating an invoice with the fixed preimage, settling the held payment.

No, Cashu is only available on the embedded-lnd and ldk-node backends, gated by supportsCashuWallet(). The implementation uses the Cashu Dev Kit Rust FFI with its own SQLite database rather than the cashu-ts JavaScript library.

The findlnurl function can match bech32-like substrings inside cashu tokens and misroute them, so handleAnything.ts detects web-wrapped Cashu tokens first. Detector order in the if/else chain is load-bearing, and new detectors should be placed as late as correctness allows.

Do not use it for backend capability matrices, settings defaults, storage migrations, architecture rationale, or debugging playbooks, which are covered by sibling Zeus skills. This reference only explains what protocols do and how Zeus implements them.