Lightning.Pub

• Name: Lightning.Pub
• URL: https://lightning.pub/
• Category: shared-node Lightning service middleware / Nostr account-and-policy layer
• Tags: bitcoin-ecosystem nostr-ecosystem
• Summary: Lightning.Pub is shared-node Lightning service middleware with a Nostr account layer. The point is who can use the node, on what terms, and through which app pools, fees, webhooks, and liquidity defaults. It is not a node baseline and not a wallet anchor. The named operator boundary around stack packaging, bootstrap posture, white-label workflow, and the broader Lightning.Pub-plus-ShockWallet ecosystem now lives in shocknet.
• What it does:
  • Runs a Lightning service stack with a Nostr-native RPC and account system for operators serving friends, family, customers, or apps
  • Uses Nostr relays for communication so operators can skip much of the reverse-proxy, DNS, firewall, Tor, and SSL busywork typical of self-hosted Lightning services
  • Automates channel management by fetching quotes from multiple LSPs and supporting bootstrap liquidity-provider flows
  • Supports application pools, user accounts, and customizable fee regimes for monetized multi-user or multi-app operation
  • Exposes static offers, webhooks, and CLINK-based offers or debits so external apps can request payments, budgets, and other Lightning actions over Nostr
  • Integrates with ShockWallet for admin pairing, guest invitations, and remote dashboard control
  • Includes an integrated watchdog meant to catch discrepancies between LND and the accounting database
• Key claims:
  • The homepage calls Lightning.Pub “the easiest and most powerful Lightning Node” and positions it for family-and-friends sharing, business operations, and node operators; the real point is shared service operation, not solo-node purity
  • The README calls Pub a “Nostr-native account system” and says it solves networking and programmability hurdles with a full Nostr-native RPC over commodity relays, which is enough to treat it as account-system infrastructure rather than a mere installer
  • First-party materials highlight automated channel management, multi-layer accounting, static offers, webhooks, CLINK app connections, and direct Lightning Address or LNURL bridging, so the useful analytical frame is service middleware with embedded wallet access
  • The warning section says the software is still bleeding edge and not recommended alongside other Lightning account systems such as AlbyHub, LNbits, or BTCPay; that caveat matters more than any marketing claim
• Whitepaper: No canonical standalone Lightning.Pub whitepaper or litepaper surfaced in this pass. The clearest source of truth was the official site, the canonical Lightning.Pub README, and ShockWallet’s first-party materials; see ../whitepapers/lightning-pub-primary-sources-2026-05-03.md.
• Sources:
  • https://lightning.pub/
  • https://raw.githubusercontent.com/shocknet/Lightning.Pub/master/README.md
  • https://shockwallet.app/
  • https://raw.githubusercontent.com/shocknet/wallet2/main/README.md

Internal linkages

• Company / operator boundary for stack packaging, bootstrap workflow, white-label posture, and the broader ecosystem shell: shocknet.
• Best upward reads for wallet-connected or API-driven Lightning control: alby and phoenixd.

Protocol / company boundary

• Keep this note on the node-side shared-service mechanism: account admission, app pools, fee regimes, webhooks, CLINK flows, liquidity defaults, and remote administration over Nostr.
• Use shocknet when the sharper question is who packages Lightning.Pub with ShockWallet, shapes bootstrap and white-label workflow, and defines the broader operator-facing trust shell around the stack.
• That split matters because how does Lightning.Pub work? and which named operator packages the easiest way to run it? are related but not identical questions.

Control surface

• Authority sits in account admission, app-pool policy, fee defaults, liquidity-source defaults, relay dependence, and how much admin reach the operator exposes to ShockWallet or outside apps.

• The named operator and packaging shell above those product mechanics now points upward to shocknet when the question is bootstrap defaults, release-and-docs workflow, or broader ecosystem packaging.

• Read it as shared-node service middleware over stronger Lightning implementations, not as a wallet or node baseline.

• Last reviewed: 2026-08-08 UTC