Reply to this note

Please Login to reply.

Discussion

🤣

I use WoS but I only keep like 100k sats in there at a time 🤷‍♂️

That's a lot 🤔

Learn to code!

Looks like NIP 57 requires LNURL which is inherently centralised... 😥

Because of DNS?

DNS, CAs, and the requirement of a public server

Handshake solves the first 2 of those issues

Going to upgrade it to bolt12 once that's available

lnurl just requires a webserver that can communicate with the LN node to generate invoices on-demand.

Can't that in theory be done with a nostr client daemon that listens to certain events from a set of relays and replies with invoices?

My point is: can't we have an entirely DNS-free lnurl spec alternative that only uses nostr? We can call it lnostr or something.

cc #[0]

how would one connect to Nostr?

Like any client, using a configured set of relays.

but that's through DNS then I guess.

What I meant was it doesn't require any LN participant to own a domain

Or we could finalize and deploy bolt12 and not need any secondary system

bolt12 requires onion messaging which also has reliability trade-offs.

I'm also hoping it works well and we don't need anything else.

NIP 57 doesn't support BOLT12 though, does it?

bolt12 isn't even spec'd yet is it? The plan is to extend nip57 once it is

🤣😅 das whai 3 nodes. for an operation. #memo

What are you talking about bolt12 is only on paper.

I think cln has an experimental version with bolt12. Saw something about that in ride the lightning when I had a cln node.

Could be wrong