This (finally) adds some amount of censorship resistance to LN Address, not to mention better security and (thanks to BOLT12) even allows users of custodial services to use their own domain for their address!
The full protocol (lightning-specific) protocol is implemented at https://git.bitcoin.ninja/index.cgi?p=lightning-resolver;a=summary nostr:note1gt9ryucy0eyn6gcez3vj5j2vgswsp70kz9mhk97egh54r4cjmzcsswpv06
👀
nostr:note1z6cwn6v5wp4c6yvzq2d8jqf8nxzrl69c2nl0f03nu434pvfqu9ls5lrp4d
This looks interesting. Resharing so I can look at it later.
Is this important on a layer that most normal humans won't transact on?
It applies equally to on-chain as it does lightning/fedimint/cashu/whatever!
All of those are made for large numbers of normies to use though. The base layer simply won't be. I don't see how the value will outweigh expanding the code and complexity. I'm not saying isn't there, I'm just not convinced.
All of those are made for large numbers of normies to use though. The base layer simply won't be. I don't see how the value will outweigh expanding the code and complexity. I'm not saying isn't there, I'm just not convinced.
#Nostr, could someone ELI5 for me? 😅
#asknostr
My first thought as I'm reading this was that Cloudflare are Google are going to be so elated to have invested in capturing massive quantities of DNS users.
I think it will not like me .. domain data is dinamically linked to well know people (kyc) .. many people on LN keep nodes behind tor addresses ... so this will work for identify user behind onion addresses? LN needs more anonymity , for example the node is disclosed on receipts; it would being need something help there, something like lnurl ; i think i'll never use it
I love how this requires homograph mitigation. Should be be simple to test if a client is not complying with these requirements.
I mean realistically people just won’t support non-ASCII hosts.
I'm not quite sure I understand what this part means? On "current scemes":
> (d) lacking open access, not allowing anyone to create a namespace mapping.
There are proposals to add proprietary APIs for, eg exchanges to expose the ability to pay their users but not users of other wallets, at least in specific contexts.
I mean, there's #Nomen https://nomenexplorer.com/ by nostr:npub19pw5egjuhcsfsv42zkjtjs6nhpm69lnv8w2dacdyez7rvacrqnds6xjtwk (name for both #bitcoin and ln, as well for peeps on #nostr).
The git web tree view is giving this error: "404 - Reading tree failed"
Oof. Which repo?
Interesting, that just seems like a gitweb bug? If you click tree on the master branch it works, wonder if my default branch is misconfigured.
Yup, this links works: https://git.bitcoin.ninja/index.cgi?p=lightning-resolver;a=tree;h=refs/heads/master;hb=refs/heads/master
I think it could be a bug, the tree link could be missing a reference to a branch.
Waste of time, is the only thing that ln exp had teach us.
But if you like wasting, keep losing.
