pull down to refresh
0 sats \ 6 replies \ @nerd2ninja 20 Feb \ on: Using DNS To Coordinate Bitcoin Payments bitcoin
First impression: Unless it is expected that the user hosts their own DNS server, this is a stupid stupid idea.
Okay so this is because of Bolt12 offers which at least makes it much more sane than what I thought it was. What was not presented, was how a user was supposed to create this DNS record without running their own DNS. Seems worth at least exploring.
It's strictly better in every way compared to the solution it is meant to replace, which is LNURL addresses.
reply
No wait, this is a stupid idea lmao. Bolt12 can replace LNURL addresses all on its own. Not having a reusable address was what LNURL was all about creating a bandaid for, so what is all of this for?
reply
Human readability.
reply
Bah humbug. Make an in wallet contact list like how we did with phone numbers.
Yeah you're just commenting on my first impression. A lot of assumptions in my first impression that didn't turn out to be the case.
reply
So first impression was the idea, edit was about it being used for Bolt12. To specify this is a dumb idea to apply to on-chain addresses.
Reading the BIP now:
"Thus, using TXT records to store Bitcoin payment instructions allows for human-readable Bitcoin payment destinations which can be trivially verified on hardware wallets and which can be resolved relatively privately."
Why would you verify this on a hardware wallet? Are you using an on-chain address? Don't do that!
reply