From 0893feb098fde5486cb8d424ea5eb1347e7cdbe2 Mon Sep 17 00:00:00 2001 From: "Dr. Tobias Baur" Date: Fri, 3 Mar 2023 11:53:50 +0100 Subject: [PATCH] Update README.md --- README.md | 17 +++++++---------- 1 file changed, 7 insertions(+), 10 deletions(-) diff --git a/README.md b/README.md index d441374..f3f9a54 100644 --- a/README.md +++ b/README.md @@ -2,14 +2,14 @@ # Satdress -Federated Lightning Address Server (with (partly) NIP57 Zap support) +Federated Lightning Address Server (with NIP57 Zap support) ## How to run -1. Download the binary from the releases page (or compile with `go build` or `go get`) +1. Download the binary from the releases page (or compile with `go build`) 2. 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. +> The Nostr private key in the parameters should be in bench32 format (`nsec..`) and it should be a new one. It is needed to sign messages only, so does not need to be your main account key. ``` PORT=17422 @@ -42,11 +42,8 @@ Maybe ask for help on https://t.me/lnurl if you're in trouble. ## Status of the Fork: -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 +- NIP57 for Nostr (ZAPS) works when using an LNBits or LND backend, other backends (sparko, lnpay, eclair, commando) still need verification of payments in waitforinvoice.go by API calls in order to sign the zap on Nostr. (Help appreciated, because I can't test them) +- Code needs some refactoring +- Needs proper testing (especially in multi-user environment) +- Credit for the inspiration by LightningTipBot code from @calle https://github.com/LightningTipBot/LightningTipBot