For wallets wanting to get a head start on implementing human-readable bitcoin names, here’s a library that handles all the DNS parts! * resolves against a local (/remote) TCP/53 resolver * resolves against a DoH/DoT resolver * creates/validates proofs

dnssec_prover - Rust

The DNS provides a single, global, hierarchical namespace with (when DNSSEC is used) cryptographic guarantees on all of its data.

It can even be run in WASM on a web page (and resolve via DoH directly)!

Provable DNS Querying

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 View quoted note →

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...

Querying DNS in a fully self-validating manner is pretty trivial, so much so you can shove it in a small webpage :) Shove Bitcoin payment instructions in TXT records and now you can get easy internet-less self-validated proofs of payment instructions! A hardware wallet can even check it and display a nice human-readable name for payments, talk about awesome UX.

Provable DNS Querying

Test looking up matt.user._bitcoin-payment.mattcorallo.com. TXT :)

On-chain: Noncustodial Lightning: Noncustodial (*) Statechains: Regulatorily Noncustodial Fedimint: Federated Custody Exchanges: Custody Easy enough?

It’d be a big miss to add transaction introspection (covanents) and not enable lightning to remove anchors entirely. Allowing the transaction broadcaster to simply reduce their balance to pay fees at broadcast-time would solve one of the biggest pain points for LN. Sadly I’m not sure that any covanent opcodes currently proposed would enable that - you need the ability to sign all outputs except the value of one, but still ensure the value is over some threshold.

This is your yearly reminder to never, ever use GoDaddy. In an a race to the bottom industry with tons of sketchy players, they differentiate as “we ran some commercials with hot women in the early 2000s when that was still kinda acceptable and people still remember our name”. They have high prices, and gouge in any possible way they can, with incredibly sketchy practices and support agents who lie to your face.

How is GitHub’s PDF viewer so bad when they could have just embedded pdf.js and moved on?