dikaios1517 on Nostr: Yep, there's two different "connections" that have to be made. One is where you will ...
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.
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.