Federated Lightning Address Server (with (partly) NIP57 Zap support)
- Download the binary from the releases page (or compile with
go build
orgo get
) - Set the following environment variables somehow (using example values from bitmia.com):
The
nsec
in this file should be a new one. It is needed to sign messages only, so does not need to be your main account key.
PORT=17422
DOMAIN=bitmia.com
SECRET=askdbasjdhvakjvsdjasd
SITE_OWNER_URL=https://t.me/qecez
SITE_OWNER_NAME=@qecez
SITE_NAME=Bitmia
NOSTR_PRIVATE_KEY=nsec213....
- Start the app with
./satdress
- If you don't know how to set env you can put the above parameters in your commandline before
./satdress
- Serve the app to the world on your domain using whatever technique you're used to
Note that DOMAIN
can be a single domain or a comma-separated list. When using multiple domains
you need to make sure "Host" HTTP header is forwarded to satdress process if you have some reverse-proxy).
If you come from an old installation everything should get migrated in a seamless way, but there is also a
FORCE_MIGRATE
environment variable to force a migration (else this is done just the first time).
There is also a GLOBAL_USERS
to make sure the user@ part is unique across all domains. But be warned that when enabling
this option, existing users won't work anymore (which is by design).
Maybe ask for help on https://t.me/lnurl if you're in trouble.
NIP57 for Nostr (ZAPS) works when using an LNBits or LND backend, other backends still need verification of payments in order to sign the zap on Nostr. (Help appriciated)
Code needs some refactoring
Needs proper testing (Multi-User and other backends)
Inspired by LightningTipBot code from @calle https://github.com/LightningTipBot/LightningTipBot