Happy to collaborate - or at least make sure it’s compatible.

Did you have a plan for invoice generation? Generate new invoice per 402/Content? I’d like to support ZAPs and be non-custodial ideally. I thought about supporting inbound webhook a from users local lightning nodes - basically they forward payment success messages which unlocks the content.

I have a concern around privacy - because you leak the pubkey - and ideally you’d only want to provide a pubkey if you’re paying or think you’ve paid.

Reply to this note

Please Login to reply.

Discussion

I'm using hold invoices on my LND node, to proxy invoice payments to any LNURL

I at the same time get excited when I see someone using hodl invoices, for the experimentation, but also sad, because of how bad hodl invoices are for lightning 😅

Once Nostr matures a little, the Nostr devs may need to help the lightning devs for a bit. Seems like lightning is a bottleneck for lots of cool stuff.

Hard problems to solve for sure, but with devs and momentum of real world use cases that Nostr can bring to life, I can see it working.

Bad why? It's only bad if they get stuck

yeah, tying liquidity across the entire route; by their very definition they are htlcs you don't want to immediately settle; short duration hodls are not problematic, but multi-hour/day ones... 😕

Have you seen this?

https://lnproxy.org/about.html

Yea it works exactly like LNProxy, my kieran@snort.social LN address is using it right now

this is super cool!

fyi: we hat this SoB project: https://blog.getalby.com/building-a-content-distribution-proxy-implementing-the-lsats-spec/

using lnurl + lsat

and there is: https://docs.ocps.tech

Bookmarked for reading first thing tomorrow

Nice. So we have some prior art. I’ll have a detailed look.

Cool, i was probably going to follow LSAT, or just use Nostr HTTP auth, didnt decide yet