Matt Corallo's avatar
Matt Corallo matt@bitcoin.ninja 1 year ago
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.
GitHub
Add BIP 353: DNS Payment Instructions by TheBlueMatt · Pull Request #1551 · bitcoin/bips
User behavior has clearly indicated a strong demand for the resolution of human-readable names into payment instructions. This BIP defines a protoc...

Replies (28)

Matt Corallo's avatar
Matt Corallo matt@bitcoin.ninja 1 year ago
It could, but luckily we don’t actually need any transport encryption to send money to people over bitcoin :) That prover does support TLSS though, if it want to use DANE for something.
Matt Corallo's avatar
Matt Corallo matt@bitcoin.ninja 1 year ago
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!
1 replies ↓
urza's avatar
urza _@urza.cc 1 year ago
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..
bumi's avatar
bumi michael@getalby.com 1 year ago
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?
Matt Corallo's avatar
Matt Corallo matt@bitcoin.ninja 1 year ago
Because there’s like 50 totally trusted and totally sketchy CAs that you have to rely on? Also DNS is quite simple, HTTPS+CAs+TLS on top is a *lot* more complexity that you can just…. Not have.
↑