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. https://github.com/bitcoin/bips/pull/1551
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/
DANE could play a role here to provide transport layer encryption without needing to trust a CA
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.
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
@jb55 @benthecarman @calle 👁️⚡👁️ What do yall think 👀👀
ECashers don't get it, too many NGO bribes paying the bills. Lightnings Nostr application layer is being built on Lightning.pub
E-Cashers <3 😘
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.
Could this support bip47 reusable payment codes? Would love to lessen the dependency on paynym.is "nameserver"
Yep! Just gotta define a bitcoin: URI query parameter. Best thing is you can even do both - one URI/name that resolves to lightning + on chain + BIP47….. sender will just pick what they support and pay it!
That's great. What do I call this? Is there a bip number?