Cowrie Research

musqet-primary-sources-2026-05-03

2 min read

Musqet primary sources — 2026-05-03

Project status in this pass

  • No canonical standalone Musqet whitepaper or litepaper surfaced.
  • The clearest current source of truth is the official site plus Musqet’s public GitHub organization and UCP Lightning-spec repository.
  • Musqet is best understood as merchant-operations infrastructure with a Bitcoin and Lightning interoperability layer, not just as a wallet or narrow payment gateway.

Primary-source snapshots

1) Official product positioning

  • URL: https://musqet.tech/
  • Key excerpt:
    • The homepage says Musqet provides “seamless card and Bitcoin payments” for customers anywhere.
    • It frames the product as both online and retail infrastructure and says merchants can settle in crypto or local currency.
    • It also says the EPOS platform spans payments, orders, stock control, customer communication, and loyalty.

2) GitHub organization posture

  • URL: https://api.github.com/orgs/Musqet
  • Key excerpt:
    • The GitHub organization description is “A Bitcoin Company.”
    • The org links back to https://musqet.tech/, tying the public code surface to the commercial product.
    • The public repositories make it easier to see that Musqet is doing more than a marketing site alone reveals.

3) Public repo mix

  • URL: https://api.github.com/orgs/Musqet/repos
  • Key excerpt:
    • The org’s public repositories include ucp-lightning-spec plus react-native-pax-library.
    • The PAX-device library suggests active interest in payment-terminal integration.
    • The repo mix supports cataloging Musqet as merchant infrastructure rather than purely as a protocol author.

4) UCP Lightning payment-handler overview

  • URL: https://raw.githubusercontent.com/Musqet/ucp-lightning-spec/main/README.md
  • Key excerpt:
    • The README describes a payment-handler specification for UCP that enables Lightning payments between autonomous agents and businesses.
    • It lists three handler families: com.musqet.bolt12, com.musqet.lnurl-pay, and com.musqet.invoice-api.
    • It says all three profiles produce the same credential: a SHA-256 preimage proving HTLC settlement.

5) Full payment-handler specification

  • URL: https://raw.githubusercontent.com/Musqet/ucp-lightning-spec/main/lightning-network-payment-handler.md
  • Key excerpt:
    • The spec says it defines how a Platform (autonomous buyer) pays a Business via the Bitcoin Lightning Network in a UCP checkout.
    • It explicitly supports BOLT12 offers, LNURL-pay / Lightning Address, and provider-mediated invoice APIs, with invoice-api intended for fiat-denominated invoices and FX locking.
    • The document is payment-provider-neutral and centers on a shared preimage-based settlement proof, which is the clearest sign that Musqet is participating in merchant/agent payment interoperability rather than only operating a closed product stack.

Working conclusion

Musqet is best cataloged as a Bitcoin merchant-operations platform and Lightning payment-handler spec author. The deciding evidence in this pass was the combination of unified card-plus-Bitcoin merchant positioning, EPOS workflow claims, public terminal-integration code, and a first-party UCP Lightning spec that bridges BOLT12, LNURL-pay, and invoice APIs into one reusable settlement credential model.

Graph View