It’s time bitcoin had a way to specify human-readable names for payment instructions.
LN Address has demonstrated the utility of such names, but it’s time to take it beyond just lightning and remove the dependence on HTTPS/CAs.
It’s time bitcoin had a way to specify human-readable names for payment instructions.
LN Address has demonstrated the utility of such names, but it’s time to take it beyond just lightning and remove the dependence on HTTPS/CAs.
🤌🏽💯🔥
This is neat.
You had me at “DNS”.
Would love to dig into this (no pun intended)
The DNSSEC proof validation can also be played with at http://http-dns-prover.as397444.net/
Does this BIP require Bolt12 as a pre-requisite?
No, it’s generic (for on chain), but for lightning you need a static invoice, so BOLT11 won’t cut it and you need BOLT12.
Can you explain this like I’m 5 please?
diff Q
how was Boltfun doing 2fa OTP to nostr DM before? any idea
People have largely figured out Tor doesn't work and bolt12 is dead on the vine as a result
Putting an npub in there to use nostr as bolt11 transport would makes sense though
why did openalias never catch on?
can we now use it now?
I mean this is basically the same thing, just a bit less polluting of a domain’s normal contents.
both require a TXT entry, don’t they?
I am mainly wondering how to push adoption. nobody cared about it back then. Afaik Electrum was the only wallet to implement it.
In your proposal would a nostr identifier also fit in?
Could this support bip47 reusable payment codes? Would love to lessen the dependency on paynym.is "nameserver"
to use it I need to buy a domain right?
I mean, to put anything on the internet you generally do…or someone has to on your behalf.
Yeah, it has drawbacks, but it is probably more realistic than some spacechain based or similar solution that doesn't rely on DNS - which I would love, but that has issues of their own..
not sure if I like it
Hi Matt, wouldn't this increase doxing risk?
saving for later
nostr:note1gt9ryucy0eyn6gcez3vj5j2vgswsp70kz9mhk97egh54r4cjmzcsswpv06