Cowrie Research

blfs-primary-sources-2026-05-02

2 min read

BLFS (Bitcoin Lightning for Shopify) primary sources — 2026-05-02

Project status in this pass

  • No canonical standalone whitepaper or litepaper surfaced.
  • The clearest current sources of truth were the official Megalith Lightning docs and the first-party GitHub repository.
  • The materials make BLFS look like reusable Shopify-to-Lightning merchant middleware built around Nostr Wallet Connect rather than a simple plugin.

Primary-source snapshots

1) Official getting-started overview

  • URL: https://docs.megalithic.me/BLFS/getting-started
  • Key excerpt:
    • The docs say BLFS “connects NWC (Nostr Wallet Connect) financial services to individual Shopify merchants.”
    • They describe BLFS as an open-source, server-side, constantly running application that talks to an NWC funding source and the Shopify API while generating customer-facing Lightning invoices.
    • They also say anyone can run BLFS, anyone can connect it to any NWC financial service, and operators may optionally charge a percentage fee.

2) GitHub repository framing

  • URL: https://github.com/MegalithicBTC/BLFS
  • Key excerpt:
    • The repo says BLFS enables Shopify merchants to receive zero-fee Bitcoin payments over the Lightning Network “without trusting any counterparty.”
    • It also shows a one-operator / many-merchants model and names example NWC services such as Rizful, Alby Hub, LNbits, Coinos, and Wallet of Satoshi.

3) Merchant onboarding flow

  • URL: https://docs.megalithic.me/BLFS/first_steps_for_merchant
  • Key excerpt:
    • The merchant docs say the merchant signs up for an NWC-capable Lightning service, obtains a receive-only NWC code, and then hands the BLFS developer three things: the receive-only NWC code, the .myshopify.com store domain, and a public brand image URL.
    • This is strong evidence that BLFS is coordinating an operator workflow around merchant onboarding, not just embedding a wallet button.

4) Developer deployment model

  • URL: https://docs.megalithic.me/BLFS/first_steps_for_developer
  • Key excerpt:
    • The developer docs recommend a low-latency cloud VPS with minimal specs such as 1 vCPU and 2 GB RAM.
    • They stress that the BLFS instance must be publicly reachable and responsive because it is generating invoices during live checkout.
    • This reinforces that BLFS is an operational middleware service, not just a static theme customization.

Working conclusion

BLFS is best cataloged as Shopify merchant-payments middleware that bridges Shopify checkout, merchant-provided receive-only NWC credentials, and Lightning invoice generation. The decisive evidence in this pass was the repeated server-side language, the explicit merchant-to-operator onboarding handoff, the multi-merchant operator model, and the public emphasis on NWC as the funding/control surface.

Graph View