Cowrie Research

cashu-pos-primary-sources-2026-05-02

3 min read

Cashu POS primary sources — 2026-05-02

Project status in this pass

  • No canonical standalone Cashu POS whitepaper or litepaper surfaced.
  • The clearest current sources of truth were the official GitHub repository, the raw README, and the published package manifest.
  • The materials consistently frame Cashu POS as merchant terminal infrastructure rather than as a simple wallet app or narrow Cashu experiment.

Primary-source snapshots

1) Official repository overview

  • URL: https://github.com/babdbtc/cashu-pos
  • Key excerpt:
    • The repository description and README frame the project as a self-hosted payment processing system using Cashu ecash, with Lightning-compatible payments and NFC tap-to-pay.
    • That immediately positions the project as merchant acceptance infrastructure, not just a consumer wallet.

2) Feature surface in the README

  • URL: https://raw.githubusercontent.com/babdbtc/cashu-pos/master/README.md
  • Key excerpt:
    • The README lists NFC tap-to-pay, Lightning invoice support, dual payment handling, built-in wallet integration, offline queuing, product catalog, tips, restaurant workflows, receipt printing, refunds, transaction export, multi-terminal sync, and device approval.
    • That breadth is the strongest signal that Cashu POS is packaging a merchant operating surface around ecash acceptance.

3) Mobile-only and operator-oriented deployment posture

  • URL: https://raw.githubusercontent.com/babdbtc/cashu-pos/master/README.md
  • Key excerpt:
    • The README says the project is designed for mobile devices, requires Expo Go on iOS or Android, and does not support web browsers because of native dependencies like NFC and secure storage.
    • This matters because it clarifies that the product is optimized for handheld merchant-terminal use instead of generic web checkout.

4) Why Cashu section and explicit tradeoffs

  • URL: https://raw.githubusercontent.com/babdbtc/cashu-pos/master/README.md
  • Key excerpt:
    • The README compares direct Lightning with Cashu and says Cashu enables offline payments, native NFC tap-to-pay, stronger privacy through blind signatures, and acceptance without the receiver being online.
    • It also explicitly notes the trust-mint tradeoff against direct Lightning self-custody.
    • That section helps explain why the project should be cataloged as merchant-POS infrastructure tuned for operational UX rather than as a generic Lightning wallet.

5) Nostr-based multi-terminal sync

  • URL: https://raw.githubusercontent.com/babdbtc/cashu-pos/master/README.md
  • Key excerpt:
    • The README says terminals synchronize product catalogs and transaction history over Nostr relays, with local SQLite storage, signed events, and conflict resolution via version numbers and timestamps.
    • It also documents sync settings like automatic sync, interval timing, retry delay, and default public relays.
    • This is strong evidence that Cashu POS is building a decentralized merchant coordination layer, not only a single-device wallet.

6) Shipped technology surface

  • URL: https://raw.githubusercontent.com/babdbtc/cashu-pos/master/package.json
  • Key excerpt:
    • The package manifest confirms dependencies on @cashu/cashu-ts, react-native-nfc-manager, nostr-tools, Expo SQLite, Expo Secure Store, expo-print, and optional Supabase tooling.
    • Those concrete dependencies line up with the README’s claims around Cashu walleting, NFC acceptance, Nostr sync, local/offline storage, receipt printing, and broader merchant operations.

Working conclusion

Cashu POS is best cataloged as a mobile Cashu merchant-terminal and Nostr-synced offline merchant control plane. The deciding evidence in this pass was the combination of NFC tap-to-pay acceptance, Lightning fallback, offline queuing, merchant wallet features, restaurant and catalog workflows, refund/export tooling, and explicit multi-terminal synchronization over Nostr.

Graph View