nostrstack-lightning

Lightning/LNbits integration for nostrstack, including regtest flows, staging/prod config, observability, and payment/zap behavior. Use when editing payment flows, Lightning provider code, or running LNbits-related tests.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 9, 2026⬇️1downloads

When & Why to Use This Skill

The nostrstack-lightning skill is a specialized integration tool designed to streamline the implementation of Bitcoin Lightning Network payments and LNbits within the nostrstack ecosystem. it provides developers with structured workflows for managing payment flows, zap behaviors, and environment-specific configurations, ensuring secure and efficient financial interactions in decentralized applications.

Use Cases

  • Integrating and debugging Lightning Network payment providers and 'zap' functionality within the nostrstack API.
  • Setting up and executing local regtest environments to simulate Bitcoin transactions and validate payment logic without real funds.
  • Configuring staging and production environments for LNbits integration while maintaining high observability and security standards.
  • Ensuring consistent webhook handling and payment state transitions across different components of the stack during development.
  • Aligning regtest flags and testing parameters between the API and gallery applications to ensure end-to-end reliability.
namenostrstack-lightning
descriptionLightning/LNbits integration for nostrstack, including regtest flows, staging/prod config, observability, and payment/zap behavior. Use when editing payment flows, Lightning provider code, or running LNbits-related tests.

Lightning + LNbits

Use this skill for Lightning/LNbits work in apps/api and related docs.

Workflow

  • Read references/regtest-flows.md for local payment/zap flows.
  • Read references/env-and-ops.md for staging/prod notes and observability.
  • Check references/testing.md for smoke/E2E commands.

Guardrails

  • Do not paste or commit secrets from ops docs.
  • Preserve webhook flow and payment state transitions.
  • Ensure regtest flags are aligned between API and gallery when testing.