Cowrie Research

lightning-pub-primary-sources-2026-05-03

3 min read

Lightning.Pub primary sources — 2026-05-03

Project status in this pass

  • No canonical standalone Lightning.Pub whitepaper or litepaper surfaced.
  • The clearest current source of truth is the official Lightning.Pub site, the canonical repository README, and ShockWallet’s first-party materials.
  • The materials consistently frame Lightning.Pub as a Nostr-native Lightning account system and service layer, not as a simple one-user wallet or generic node package.
  • The public materials also make clear that the stack is still bleeding-edge operational software with meaningful deployment caveats.

Primary-source snapshots

1) Official site

  • URL: https://lightning.pub/
  • Key excerpt:
    • The homepage calls Pub “the easiest and most powerful Lightning Node.”
    • It positions the product for family-and-friends sharing, businesses, and node operators.
    • It highlights Nostr-native accounts, automated channel management, multi-layer accounting, static offers, webhooks, CLINK app connections, and a two-minute setup flow.

2) Canonical repository README

  • URL: https://raw.githubusercontent.com/shocknet/Lightning.Pub/master/README.md
  • Key excerpt:
    • The README says Pub is a Nostr-native account system designed to make running Lightning infrastructure for friends, family, or customers easier than before.
    • It says Pub solves networking and programmability hurdles with a full RPC that is Nostr-native and uses Nostr relays for communication.
    • It documents zero-network-configuration operation, automated channel quotes from multiple LSPs, bootstrap peering, user/application accounting layers, Lightning Address support, one-line deployment, and custom relay or liquidity-provider configuration.

3) Official site developer API section

  • URL: https://lightning.pub/
  • Key excerpt:
    • The site’s developer section shows CLINK SDK examples for requesting offers, paying with debits, managing offers, and requesting budgets.
    • This is strong evidence that Lightning.Pub is not only an operator dashboard but also an app-integration layer for machine-readable Lightning workflows.

4) ShockWallet homepage

  • URL: https://shockwallet.app/
  • Key excerpt:
    • The ShockWallet homepage says the wallet is part of an open-source stack for sharing a node with friends and family over Nostr.
    • It highlights synced multi-device usage, line-of-business-oriented static offers, and direct links to Lightning.Pub.
    • This helps show that Lightning.Pub is designed to be consumed through a dedicated client surface, not merely a background daemon.

5) ShockWallet repository README

  • URL: https://raw.githubusercontent.com/shocknet/wallet2/main/README.md
  • Key excerpt:
    • The README says ShockWallet is the first wallet to use Nostr-based accounts for Lightning Network connections.
    • It says Lightning.Pub and ShockWallet make connecting to a node as easy as pasting an nprofile, support guest sharing, multi-device sync, and recurring or pre-authorized payments.
    • It also says ShockWallet is the reference wallet client for Lightning.Pub and includes the beginnings of a node-management dashboard.

Working conclusion

Lightning.Pub is best cataloged as a Lightning service control plane built around a Nostr-native account system. The deciding evidence in this pass was the recurring combination of multi-user account layers, Nostr-relay communication, automated channel sourcing, bootstrap liquidity, CLINK-based app integration, static offers and webhooks, one-line deployment, and a dedicated reference client in ShockWallet. The key distinction is that the project is packaging shared-service Lightning operations and external app connectivity, not merely helping one user run a personal wallet or node.

Graph View