If I have the same npub set up on two different clients, and each client has a different wallet set up, which wallet gets the zap?
Maybe someone smart on #asknostr knows the answer.
Discussion
Depends on what I'm seeing in my client. I see Geek@primal.net so it would go there.
Excluding built-in wallets, zapping you directly on notes would send to the ln address that you set in the client you sent it from.
I assumed it had to be based on the client but wasn’t sure. Thanks!
Zaps are sent to you using whichever lightning address is listed in your profile note (kind 0) which is not client specific.
That said, two people COULD see different lightning addresses listed for you if you have ever changed what lightning address is in your kind 0 note, and that change didn't get propagated out to a wide enough range of relays.
For this reason, I would recommend setting up a redirection service with something like nostrplebs. or nostrcheck.me, where you can keep one lightning address listed in your profile at all times, broadcast it out as widely as possible, and then change the wallet that address redirects to whenever you want/need to change wallets.
For instance, I generally receive zaps to my own node, but if my node is down for some reason (happens occasionally), I can easily go into my settings at nostrplebs.com and have my zaps sent to my nostr:nprofile1qyt8wumn8ghj7un9d3shjtnrda5kummn9e5k7tcqyzagpxgxvmhskm6t55zex3a7kyey9ys723nfu6qqvn9825jk5836v8xsdxk wallet instead until I get my node back up, without worrying that some folks might still be trying to zap my node wallet because an update to my kind 0 didn't make it out to all of the network.
It didn’t even occur to me that it would be the info in the kind 0 event, thank you! Love the redirection idea, looking into this now.
Yep, there's two different "connections" that have to be made. One is where you will be receiving your zaps to, and that is entirely based on what you have listed in your kind 0, regardless of what client you are using or whether it has a built in wallet. That's the only way to do it so that users can find where to pay you regardless of what client THEY are using.
The other is what wallet you will be sending zaps FROM. That connection IS client specific. In Primal, that will default to the built-in wallet, if you have it set up, or you can switch it to some other Nostr Wallet Connect (NWC) enabled wallet, if you are on Android. Some web apps have an ecash wallet built in, like iris.to. Others will connect to your Alby extension automatically for zaps, such as Primal web and nostrudel.ninja. Others require you to connect the client to a wallet for zapping using NWC, like Amethyst.
In all of these, OUTGOING zaps are set up on a per-client basis, and INCOMING zaps are set up for all clients at once using your kind 0 profile note.
Yeah this makes perfect sense. Been using Primal since basically I got on Nostr and it abstracts so much away that some things were just not making sense as as spun up a relay and started testing out new other client options. Now that you explain it as you did, it just seems so obvious 🙏