Nice. Yeah. Looks good. So it seems like when you zap, it still launches the wallet, but allows the nostr client to track zap activity. Is that right? And I imagine the next step would be tighter client/wallet integration so we don’t have to exit the client.

Reply to this note

Please Login to reply.

Discussion

Maybe think of it a little broader. Nostr is a protocol and there are many apps implementing it according to the standards - Damus, Nostrgram, etc. are nostr clients. Another function is the wallet (Wallet of Satoshi, Strike, others). It is good that these can be separate so we have choices. NIP57 extends the standard to allow the different apps to "see" the Zaps, the zap becomes its own transaction. I don't think there can be any greater integration than Damus and WoS (in their TestFlights) can have. The next tighter step might be for Damus to have a Lightning wallet built in, which has been hinted at. But its good to try different clients and different wallets to learn how they all work

I dunno. I personally wouldn’t want a wallet in every client. I’d prefer to link a wallet to a client via delegation. That way when I zap in Damus, WoS knows it has permission to make the payment. The pros being, I can unlink at anytime and I don’t have a ton of balances out there for all of the clients I use.

Correct. You have choices, that was what I was trying to say. As a choice, you might *want a wallet built in to the Nostr client for one-click Zaps, fire and go. When it is seperate, you have more choices, but it requires more clicks. All user trade offs which is a good thing. I would like to use a self custody wallet but I am chosing WofS for convenience.