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.

Replay attacks are important to consider with Nostr Wallet Connect implementations. The NWC request events are ephemeral, however they can come back at anytime. Keeping track of what NWC request event IDs have been run (and seen) is especially important for payment commands to stop both accidental or malicious attempts at duplicate payments.

The `nostr+walletconnect` connection string should include `://` and not just `:` to work with the QR code scanning and link handling in #amethyst and Stacker News. Amethyst will silently fail, unfortunately. The specification did not mention this until yesterday in the example. I don't think lightning URLs for invoices and LN addresses use `//`. Does it matter?

This is a great book that clarifies a lot of what "End the Fed" means.

End the Fed

Though, I think it could have a better title such as "End the Banking Monopoly".

The necessary feature to support zaps with phoenixd have landed in release v0.1.5.

GitHub

Release v0.1.5 · ACINQ/phoenixd

What's Changed Add official Dockerfile by @pm47 in #17 Add authentication to webhook calls by @pm47 in #34 Add descriptionHash parameter to create...

Working on adding NWC support for phoenixd to:

GitHub

GitHub - braydonf/satdress: Lightning Address Server with Nostr Wallet Connect and Zaps.

Lightning Address Server with Nostr Wallet Connect and Zaps. - braydonf/satdress

A 5k run and then steak for lunch. Today is a good day.

Running a private relay with strfry, what else is needed to support the outbox model?

This could be a useful library for writing policies for the strfry relay.

GitHub

GitHub - jiftechnify/strfrui: A framework for writing strfry's event sifter (write policy) plugin in Go.

A framework for writing strfry's event sifter (write policy) plugin in Go. - jiftechnify/strfrui

The next release of phoenixd should have `descriptionHash` as a parameter for creating invoices, as needed for zaps. Now running phoenixd with this branch:

GitHub

Add `descriptionHash` parameter to `createinvoice` by pm47 · Pull Request #50 · ACINQ/phoenixd

A new parameter descriptionHash has been added to createinvoice, it takes a 32-bytes hex string. Either description or descriptionHash must be prov...

Cool, @Alby has a Go library for Nostr Wallet Connect!

GitHub

GitHub - getAlby/nostr-wallet-connect: Nostr Wallet Connect (NIP-47) application to allow apps to connect to your node

Nostr Wallet Connect (NIP-47) application to allow apps to connect to your node - getAlby/nostr-wallet-connect

This will make a great addition to:

GitHub

GitHub - braydonf/satdress: Lightning Address Server with Nostr Wallet Connect and Zaps.

Lightning Address Server with Nostr Wallet Connect and Zaps. - braydonf/satdress

North Cascades, Washington.

I finally have a self-custodial wallet for recieving payments to a Lightning Address and handles Zaps! It is using a Phoenix wallet for a server: https://phoenix.acinq.co/server And a web service for LN Address support and Zaps:

GitHub

GitHub - braydonf/satdress: Lightning Address Server with Nostr Wallet Connect and Zaps.

Lightning Address Server with Nostr Wallet Connect and Zaps. - braydonf/satdress

$ docker system prune (minutes later) Total reclaimed space: 40.56GB docker 😂

It's refreshing to have indoor spaces feel more like the outdoors.

Compiling phoenixd on Debian or similar is turning more complicated than expected.