I don't think people understand how powerful this Wallet Connect NIP is.
Here are a few ideas that can be built it top of it:
- Setup recurring payments in native Nostr (think monthly subscriptions of your favorite apps)
- Send sats in other functions (i.e. every like automatically sends 10 sats to the author)
- Send zaps to all replies of a post, or to all your follows/followers.
- Send zaps proportionally to time spent per post/thread by the end of the day/month.
There is so much it can do.
WoW! 🤯
👏👏👏🥳🥳🥳
Je m'en vais voir. Je vais bientôt créer un compte et m'abonner à toi. Merci pour l'information que tu partages.
Wow sounds exciting.
🔥⚡👀
#[1]
👀
#[0]
Sphinx chat already has recurring payments. And creators can engage directly with their supporters using tribes 😉
👀
Nothing you can't do with a regular API call. It sounds to me like using nostr for the sake of using nostr.
I don't believe this kind of messages should be part of the protocol, adding every single edge case to the protocol over complicates it, overcrows network and relays:ñ; and slowly makes our private keys a single point of failure.
I just implemented a wallet in Nostros by using lndhub API calls and I never had the need of using nostr.
That's true for everything in Nostr. You can do all this without Nostr, in regular calls.
The goal of the NIP is to make sure Nostr clients don't need to understand the API of each LN connection type out there.
It significantly decreases implementation time. I added it yesterday to Amethyst in under 1 hour.
Cool
Wait, isn't it true that Nostr Connect is not required for anyone? i.e. all clients can go on with their lives without ever caring about Nostr Connect and still get the same experience?
Maybe I'm a nostalgic and I miss when the protocol was really simple 😛 you can basically run with only NIP-1, I'm just wondering if there is a point where it's just too much for relays to deal with everything at the same time, everywhere
I think people see the potential, but are also worried about vendor lock-in.
Imagine every app having its own wallet 'because powerful features". It would be a mess.
the point of doing it over nostr instead of over the LNDhub API is to avoid vendor lock-in.
That only works for apps that support this NIP, which is probably limited to Nostr clients.
Lightning wallets have a much broader use case.
Thats another reason to be a NIP. All of this is saved on relays. Any client can just implement it and move the user forward.
Actually, this is exactly what you will see. 👀 Just a hypotheses. Think loyalty programs.
I am a willing Test Subject...
69 is fine. It is Thee Pickle 🥒 Tickle 🤗 Zap ⚡
But 69,000 would be The Mother of all Pickle 🥒 Zaps ⚡
Feel free to experiment on me as You wish.
I can handle it. I will use it to buy Diesel Fuel... 😂
⚡ zapping ⚡
In
4...
3...
2...
lnbc690u1pjpkq3zpp55f8fdk62fa0r663y054lav2h3a3lek9pmxtm95uzyg0l97f56tlqdqu2askcmr9wssx7e3q2dshgmmndp5scqzpgxqyz5vqsp5qv57fej3z533q9fqk8we0yyrk8hpzeakmmn658k7h7edgkmg2nmq9qyyssqp2y4rcyty9dsfvya7kltpr8s44s5905jwqg9nxtd9c6wy62qc784rtssy2yf5gggyux34dhef0z9pmlqqjuhj33xjvena60slasxxuqp8s86m8
Best take. Magic.
#[0]
What about NIP-46, Nostr Connect? Do you like it too?
I initially hated it. Because it creates a layer 2 protocol (JSON inside content) that can be anything... It's not a simple and fun as Nostr main structures.
But its growing on me.
Thank you for saying that. I also hate it for the same reasons. But the goal is noble and since no one has made anything else better it I think it is good to have it.
One of the reasons the Wallet Connect doesn't have a generic json "method", but multiple event kinds to make it a little bit more native to Nostr payloads.
Gotta love the transformative energy of Nostr. My mind is blown every day seeing shit like this. 💜💜
#[0]
⚡💜
#[0]
Did you see that? 👀
#[1]
