What needs to be improved with NIP-60?
Discussion
How does a new npub set up a NIP-60 wallet for sending and receiving zaps?
Well I guess that’s technically the beauty they don’t. it already comes with the npub, now some clients I guess should adopt that if the LUD16 is empty they still could get zapped straight to their nip-60 wallet. ✌️
I'm now knowledgeable on the details, but that sounds right. Essentially you're saying there should never be a "cannot zap, no wallet" message from a client, because lack of a LUD16 should fallback to NIP-60.
Even before that, though, it seems most clients don't even provide a mechanism to *opt* to zap to NIP60, right?
Correct in my book if the user sets a lightning address bolt 11 or bolt 12 offer or one of those bip353 ones that should be used. If nothing is provided ecash send to npub ( nip-60 ) should be fallback so the users doesn’t even see the difference when zapping.
Not that I have anything like that implemented 😂 but makes most sense I just think/fear that some clients might not want to adopt this method for fear of making lightning adoption even less used. And the nip-60 should still be only used for very small amounts, having clients just be able to access the wallet without any guardrails could be a great honeypot 😂
Don't invest blindly in stocks or crypto when you do not have a proper guide. I lost 30k trying to trade on my own but ever since Mrs Susan J Demirors stepped in, I have been making huge profits. I made over 450k since October. She is always available to tell you more about investing and give a guide on how to trade visit her on Email susandemorirs@gmail.com and her WhatsApp +1 (472) 218-4301
On the education side some clear guidance to developers regarding Apple App Store policies—why Nostr apps with NIP-60 wallets and zapping of notes may not stand a great chance of being approved, what the PWA environment on iOS currently affords, etc.
Happy to contribute a write up.
Do we need two separate kinds (17375, 10019) for the wallet and mint information? Couldn't we have one event / kind where the content is encrypted and contains the priv key, the tags contain the mints, relays, and pub key?
That way anyone could retrieve the public information from the event, but only the wallet creator could decrypt the priv key from the content.