I just completed a Zap from #Amethyst from #phoenixd with Nostr Wallet Connect.
Work-in-progress for #NWC support for phoenixd is here:
https://github.com/braydonf/satdress/tree/nwc
I also added a CLI tool for exporting the NWC connection string and QRcode from the terminal.
Is it possible to open and manage channels with other nodes or is it a single phoenix channel only type server?
I don't think there are many options for channel management as it's managed. That will be better handled by another backend like CLN or LND, that should also be supported.
Wow, amazing!! Could make a docker image or container please if possible?
Did you see this nostr:npub1ky4kxtyg0uxgw8g5p5mmedh8c8s6sqny6zmaaqj44gv4rk0plaus3m4fd2?
Will you try to make a docker image again?
Complied the app now on Ubuntu, how do you generate the nwc pibkey, relay and secret? Could I import this from amethyst or do I have to run my own nostr relay and nwc service?
I haven't added it yet, however there should be a command with satdress-cli to create that secret for the NWC connection as well as for the server.
Both should be new keys. Both are 32-byte random hex strings (not nsec encoded).
Ok will look into satdress.cli and wait what you will magically implement;-)
This command will now do it:
`./satdress-cli nwc keygen`
Thanks very much, I will try!
sorry i dont really get it, this command genartes a public key and a pricate key both hex and nsec , which one would be secret and which is the pubkey?
Yeah that is for creating a private key for the relay. For the wallet secret, use the hex private key, of a new key. There could be two commands for each, with different output, for clarity.
ah i see got it...seems to work now, but would have to expose still...
love testing. THX!
Yo that works!!!
Got this message back in return, something not right yet...
8RZ2T3KYpdeJptb+kslU3tiwtXCGVp42pnWnwPNzMfmt50aCoTSRxUSukPEXnp5SVk2LlryUrqajMNxaYMoVKl6HrPUZEFQf6naE7PABEhm32jTBS5LQy1Q43INMfcgo6HzB6NFWzscPp1zbcqVs3AdoyiSCi6nhX/k5unbTZScfs9HNHtINhsiE7Js46eUPDvLAcsU+x22wdC7WL9F4t6bhJEtrqqJ3S2ywXDZrWK1xRYC7evFq9M5V3huFBX6YCooMCXiQRPryDag0yp91duVe6Db9LjoLnm/AKjY5Dvh0S+YaOmZFyZTZN5TWBqX4sF3Yp51ms5UWn+ohjzfoKhh0RH4kGlFzut+4B4LX8JVFin87lqvoMwHCeyMvLafDRZVXgle6wkNBGjSSNSICGs8UfGC9XTS4GMMuvbl31eiL5obTOMYZg9V+mkvPEuCmTuViKc0u9OOHdDmtfiJ+hReAA8DHBTy7CRAARjQ+qxsUJZB7v5TIZoL7WPzy8FlItV2NOYJYVs+GHy6EKuOO3R5lovaksS94MSMTWj5ZF9H+OfD9ma+W3bJ1psTcYfxHLQyKijhU83RkMMJZPpZDDX7oXBB2VAKzhfktbIYK9s0Ohli3/MYxHAbhWH2mg+SS?iv=Z+NSnOZC+1usIPW5+WtQLg==
🤣😅😆
The specification doesn't require running your own relay, however it is recommended.
https://github.com/nostr-protocol/nips/blob/master/47.md#using-a-dedicated-relay
Ok I have my own relay running on Umbrel, maybe I could utilize it for that...
Shall we list it here?
Sure. The name may change later, however the url should still work.
