Replying to Avatar Alex Gleason

Well I built out what I think are the right Nostr abstractions here: https://nostrify.dev/

Can't guarantee it will solve all your problems, but I believe it's at least the right mental framework. Lightning is still hard just because Lightning is hard.

thanks! I've looked at Nostrify a bit in the past but not this time around on this project. I'll look at it again.

Lightning is so annoying that I'm wondering if going straight to nutzaps isn't actually easier... does nostrify handle ecash/nutzaps?

Reply to this note

Please Login to reply.

Discussion

Nutzaps is harder to implement than regular zaps. We implement both in Ditto, but there is no "easy way" solution for everyone else yet.

Here, you inspired me to rework my zaps implementation and add a doc for it: https://nostrify.dev/zaps

Lol fuck dude, what timing. I just reached the end of my rope trying to get nostr-tools and NDK to play nicely together for nip57.

nostrify here I come! this looks incredible.

the big question... will this take my existing NDK signer, or would I need to rip all that out...?

Have NDK generate the zap request event however it does it, then you can pass it directly into lnurl.getInvoice​.

Basically you can use this LNURL module with any other library or framework.