Satdress

• Name: Satdress
• URL: https://github.com/nbd-wtf/satdress
• Category: Lightning Address infrastructure / federated wallet-address server / self-hosted LNURL-pay middleware
• Tags: bitcoin-ecosystem
• Summary: Satdress is a self-hosted Lightning Address server. Small tool, but a real one. It lets an operator issue and route user@domain endpoints across one or more domains while choosing namespace and migration policy. Useful note because it exposes the server-side layer behind Lightning Address issuance, not because it invents a new payment primitive.
• What it does:
  • Runs a self-hosted server that turns one or more owned domains into Lightning Address endpoints for receiving payments
  • Lets operators configure the service through environment variables such as PORT, DOMAIN, SECRET, SITE_OWNER_URL, SITE_OWNER_NAME, and SITE_NAME
  • Supports multi-domain operation from a single instance when the reverse proxy forwards the Host header correctly
  • Exposes a GLOBAL_USERS option to enforce unique usernames across all configured domains
  • Includes migration behavior for older installs plus an optional FORCE_MIGRATE flag for explicit migration runs
  • Ships as a lightweight Go application with downloadable binaries and a public releases history showing ongoing compatibility fixes
• Key claims:
  • The canonical README explicitly calls Satdress a “Federated Lightning Address Server,” which is the clearest statement of scope in the primary materials
  • The README says anyone can run the app on their own domain with a small set of environment variables, which keeps the note firmly in self-hosted infrastructure rather than managed wallet territory
  • The DOMAIN and GLOBAL_USERS settings make the real operator surface obvious: multi-domain routing and namespace policy live with whoever runs the server
  • The documented migration path and release notes suggest this is meant for real operators managing upgrades and backend compatibility, not just a toy demo
• Whitepaper: No canonical standalone Satdress whitepaper or litepaper surfaced in this pass. The clearest source of truth was the GitHub repository README plus the public releases history, which together document the deployment model, configuration surface, and evolving backend compatibility; see ../whitepapers/satdress-primary-sources-2026-05-03.md.
• Sources:
  • https://github.com/nbd-wtf/satdress
  • https://raw.githubusercontent.com/nbd-wtf/satdress/master/README.md
  • https://github.com/nbd-wtf/satdress/releases

Internal linkages

• Best anchors: lnurl, bip-353, and lightning-pub.

Control surface

• Namespace policy, owned domains, backend wallet-or-node routing, and migration behavior sit with the operator.

• Treat Satdress as self-hosted Lightning Address plumbing, not a broader wallet platform.

• Last reviewed: 2026-05-28 UTC