Cowrie Research

satdress-primary-sources-2026-05-03

2 min read

Satdress primary sources — 2026-05-03

Project status in this pass

  • No canonical standalone Satdress whitepaper or litepaper surfaced.
  • The clearest current source of truth is the canonical GitHub repository, its raw README, and the public releases history.
  • The project is primarily documented as self-hosted Lightning Address server software rather than as a broader marketing-led product.

Primary-source snapshots

1) Canonical repository / README

  • URL: https://raw.githubusercontent.com/nbd-wtf/satdress/master/README.md
  • Key excerpt:
    • The README calls Satdress a “Federated Lightning Address Server.”
    • It says operators can run the binary, set environment variables like PORT, DOMAIN, SECRET, and SITE_NAME, then expose the app on their own domain.
    • It positions the software as the server-side layer for receiving Lightning payments at user@domain.com non-custodially.

2) Multi-domain and namespace behavior

  • URL: https://raw.githubusercontent.com/nbd-wtf/satdress/master/README.md
  • Key excerpt:
    • The README says DOMAIN may be a single domain or a comma-separated list of domains.
    • It says reverse proxies need to forward the Host header for multi-domain mode to work correctly.
    • It also documents a GLOBAL_USERS option that enforces uniqueness of the user@ portion across all configured domains, with an explicit warning that enabling it breaks existing users by design.

3) Upgrade / migration behavior

  • URL: https://raw.githubusercontent.com/nbd-wtf/satdress/master/README.md
  • Key excerpt:
    • The README says old installations should migrate seamlessly.
    • It also documents a FORCE_MIGRATE flag for forcing a migration on first run when needed.
    • This is a useful operational clue that the project is intended to persist state across real upgrades rather than only serve as a throwaway demo.

4) Public releases history

  • URL: https://github.com/nbd-wtf/satdress/releases
  • Key excerpt:
    • The releases page shows first-party notes mentioning LNbits support fixes, updated Core Lightning / commando support, Eclair support, and automatic builds on GitHub Actions.
    • These release notes help confirm that Satdress sits in the Lightning backend compatibility layer and is maintained with several node or wallet-adjacent integrations in mind.

Working conclusion

Satdress is best cataloged as self-hosted Lightning Address and LNURL-pay infrastructure. The deciding evidence in this pass was the repeated combination of self-hosting instructions, explicit multi-domain support, namespace-management options like GLOBAL_USERS, migration behavior, and releases that reference compatibility with LNbits, Core Lightning / commando, and Eclair.

Graph View