Cowrie Research

shockwallet-primary-sources-2026-05-03

3 min read

ShockWallet primary sources — 2026-05-03

Project status in this pass

  • No canonical standalone ShockWallet whitepaper or litepaper surfaced.
  • The clearest current source of truth was the official homepage, the canonical repository README, the SHOCKNET site, and the SHOCKNET GitHub organization.
  • The materials consistently frame ShockWallet as a Nostr-native client for shared-node and app-connected Lightning operations, not as a simple one-device consumer wallet.
  • The public materials also show that ShockWallet sits inside a broader SHOCKNET stack alongside Lightning.Pub and CLINK.

Primary-source snapshots

1) Official homepage

  • URL: https://shockwallet.app/
  • Key excerpt:
    • The homepage calls ShockWallet “The Lightning wallet for friends, family, and business.”
    • It says the wallet is “part of an open-source stack for sharing your node with friends and family, over Nostr.”
    • It highlights synced multi-device use, static offers with line-of-business features, and direct linkage to Lightning.Pub.

2) Canonical 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 ShockWallet supports connecting to multiple nodes simultaneously, recurring payments, and pre-authorized external application or service payment requests.
    • It describes multi-device sync via NIP-78, nprofile-based connection to a node, and a single codebase shipping to web, Android, and iOS.

3) Lightning.Pub README

  • URL: https://raw.githubusercontent.com/shocknet/Lightning.Pub/master/README.md
  • Key excerpt:
    • The Lightning.Pub README repeatedly positions Pub as a Nostr-native account system for serving friends, family, or customers.
    • It documents ShockWallet as the companion client path for this stack, which helps confirm ShockWallet’s role as an operator and guest-facing wallet layer rather than only a standalone app.

4) SHOCKNET site

  • URL: https://www.shock.network/
  • Key excerpt:
    • The SHOCKNET site says users can “Build your empire on Lightning and Nostr.”
    • It highlights Lightning.Pub, Nostr identity management, and monetized data vending machines, which helps explain the broader product posture around interoperable Lightning-and-Nostr infrastructure.

5) SHOCKNET GitHub organization

  • URL: https://github.com/shocknet
  • Key excerpt:
    • The organization overview says SHOCKNET builds applications and services for the Bitcoin Lightning Network.
    • It describes wallet2 as software to connect to multiple Lightning nodes via LNURL and NOSTR.
    • It also shows adjacent first-party repos for Lightning.Pub, CLINK, Bridgelet, and related components, reinforcing that ShockWallet belongs to a broader infrastructure stack.

Working conclusion

ShockWallet is best cataloged as a Nostr-native wallet-and-node control plane. The deciding evidence in this pass was the recurring combination of multi-node connection, nprofile onboarding, multi-device sync, shared-node/friends-and-family positioning, recurring and pre-authorized payment flows, static offers, and its role as the reference client for Lightning.Pub. The key distinction is that ShockWallet is packaging the client operating layer for shared Lightning infrastructure and app-connected payment workflows, not merely a mobile wallet for one user on one device.

Graph View