Cowrie Research

shocknet

5 min read

SHOCKNET

  • Name: SHOCKNET
  • URL: https://www.shock.network/
  • Category: Lightning-and-Nostr operator / shared-node wallet-stack company / CLINK-and-white-label payments infrastructure shell
  • Tags: bitcoin-ecosystem nostr-ecosystem
  • Summary: SHOCKNET clears the bar for a company note because the useful question is no longer only what do Lightning.Pub and ShockWallet do? but which named operator packages the shared-node stack, ships the wallet and node releases, runs the bootstrap and white-label story, frames CLINK as the app-facing integration layer, and decides how much of the Lightning-and-Nostr workflow feels turnkey versus self-hosted? Keep the project notes on Lightning.Pub and ShockWallet as product-layer notes; this note is for the operator boundary that makes the stack cohere.
  • What it does:
    • Packages SHOCKNET as a Bitcoin-only, Nostr-native, fully open-source stack for running shared Lightning nodes, wallets, app integrations, and adjacent Lightning-native products
    • Ships Lightning.Pub as the node-side shared-service layer that turns one Lightning node into a multi-user or multi-app service over Nostr
    • Ships ShockWallet as the cross-platform wallet and client shell for joining or managing Lightning.Pub nodes across web, iOS, and Android
    • Frames CLINK as the app-facing Lightning-over-Nostr interface for offers, debits, delegated permissions, and structured payment workflows without a separate web-server middle layer
    • Markets optional bootstrap and shared-node onboarding paths so users can start on a hosted or trust-based path before migrating toward their own node infrastructure
    • Sells a white-label and operator-facing packaging story rather than only publishing raw open-source repos, which makes the organization itself relevant as a support, distribution, and integration boundary
  • Key claims:
    • The SHOCK.network homepage says the company built the Lightning-Nostr stack so others can run shared nodes, ship apps, sell data, which is the clearest first-party statement that this is an integrated operating stack rather than one isolated wallet or node project
    • The same homepage says Lightning.Pub turns your node into a multi-tenant service and that the suite gives operators the levers to control your node, your keys, your revenue, which makes the operator boundary analytically useful above the individual product notes
    • The ShockWallet site says SHOCKWALLET gives users self-custody, shared nodes, multi-account management, business logic, and explicitly offers bootstrap, self-hosted, and trusted shared-node modes, which means the company is packaging multiple trust models rather than publishing one neutral wallet binary
    • ShockWallet’s FAQ says Lightning.pub is the engine behind ShockWallet and that both are part of the SHOCKNET open-source ecosystem, which is the cleanest first-party evidence that the named organization matters separately from either product note alone
    • The Lightning.Pub homepage and README both position the product for family-and-friends sharing, business operations, remote node management, webhooks, and app connectivity over Nostr, which makes the broader packaging and deployment shell matter more than a single daemon release
    • The Lightning.Pub README says operators can bootstrap peering, share guest nprofile connection data, and pair administrators through ShockWallet, which is useful evidence that SHOCKNET controls a real user-and-operator onboarding path across the stack
    • The ShockWallet README says an optional bootstrap node is default on mainnet for new users and describes ShockWallet as the reference client for Lightning.Pub with multi-device sync and recurring-payment automation, which reinforces that the company boundary matters for default trust posture and migration workflow
  • Whitepaper: No standalone SHOCKNET whitepaper is the point here. The strongest primary materials for this pass were the SHOCK.network homepage, Lightning.Pub and ShockWallet landing pages, and the canonical Lightning.Pub and ShockWallet READMEs captured in ../whitepapers/shocknet-primary-sources-2026-08-08.md.
  • Sources:

Internal linkages

  • Product-layer notes: lightning-pub and shockwallet.
  • Useful company-layer comparisons: alby, acinq, and lightspark.
  • Keep the product notes separate from this operator note: Lightning.Pub is the shared-node middleware question, ShockWallet is the client-shell question, and SHOCKNET is the named organization that packages the stack.

Protocol / company boundary

  • Keep lightning-pub focused on the node-side shared-service mechanism: account admission, app pools, fee regimes, webhook and CLINK flows, liquidity defaults, and remote administration over Nostr.
  • Keep shockwallet focused on the client-side access shell: shared-node onboarding, recurring permissions, multi-device sync, and the exact wallet UX through which that authority reaches users.
  • Keep this note focused on SHOCKNET as the named operator that publishes the integrated stack story, ships the branded products together, shapes bootstrap and white-label workflow, and decides how much of the package is turnkey versus purely self-hosted.
  • That split matters because how does Lightning.Pub work?, what does ShockWallet expose?, and which organization controls the packaged trust and distribution shell around them? are related but not identical questions.

Control surface

  • Practical leverage sits in bootstrap-node defaults, shared-node packaging, release and documentation workflow, CLINK framing, white-label go-to-market, and the degree to which operators or end users are pushed toward first-party onboarding paths instead of assembling their own stack from lower-level components.

  • Even with strong self-custody rhetoric, SHOCKNET still matters because the easiest way into the stack, the reference wallet, the node distribution, and the business-facing packaging are all coordinated under one branded organization.

  • Treat SHOCKNET as the named operator shell around a Lightning-and-Nostr stack, not as a neutral protocol primitive and not as just a marketing umbrella.

  • Last reviewed: 2026-08-08 UTC

Graph View

Backlinks