I keep removing my nwc configuration for the same reason. It would be nice if Amethyst (and other Nostr clients) could support multiple nwc connections at once and maybe even fallback from one wallet to another. It's been a while since I tagged nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z on a random request.

Reply to this note

Please Login to reply.

Discussion

I like giving zaps more friction because I dislike accidental zaps.

I get it. NWC also makes me a bit uneasy. Still... it's bloody convenient, especially in split zap-like scenarios (e.g., it's ironically painful to zap Amethyst devs from Amethyst itself without NWC).

I wish NWC enabled wallets made it easier to use my own relay for NIP-47 events. I was experimenting with adding a personal payment relay to Haven (based on nostr:npub1utx00neqgqln72j22kej3ux7803c2k986henvvha4thuwfkper4s7r50e8’s payment relay), but it’s a bit pointless unless you're running your own NWC-enabled payment infrastructure. I mean, I can easily forward events to other relays, but the whole thing is pointless if the wallet doesn’t generate a proper nostr+walletconnect:// URL with the relay address in mind, write a Kind 13194 to it, read 23194 requests from it, write 23195 responses back to it, send notifications to it, etc. The whole setup couples the wallet and relay pretty tightly.

In theory, this could be configurable though. The wallet could take one or more relay addresses.

nostr:npub12ekpvme6m2cv37a9mgq4kzemej8tx6ttg40j582rh77ewpvkg65qj8tq0f I know this is a huge ask, and not something a lot of users would need (most folks this deep into Lightning/NWC are running non-custodial wallets) but is there any chance you could add the possibility of configuring extra relays on Coinos? It would be awesome for those running personal relays.

It is convinient. I use it for recurring payments, just not zaps anymore.