# Human Readable Bitcoin Payment Instructions **URL:** \ **Category:** Protocol Design\ **Created:** [February 11, 2024, 1:11am UTC](https://delvingbitcoin.org/t/human-readable-bitcoin-payment-instructions/542 "2024-02-11T01:11:04Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![MattCorallo](https://delvingbitcoin.org/letter_avatar_proxy/v4/letter/m/e47c2d/32.png) [@MattCorallo](https://delvingbitcoin.org/u/MattCorallo)\ **Post date:** [February 11, 2024, 1:11am UTC](https://delvingbitcoin.org/t/human-readable-bitcoin-payment-instructions/542/1 "2024-02-11T01:11:04Z")
Various Bitcoin and other cryptocurrency applications have developed human-readable names for payment instructions over time, with marketplace adoption signaling strong demand for it from users. Having a standard way to resolve a human-readable name into Bitcoin payment instructions is a very useful primitive. I’ve written up (and implemented) a draft BIP to do this using DNSSEC at [bips/bip-XXXX.mediawiki at d46a29ff4b4ac27210bc81474ae18e4802141324 · TheBlueMatt/bips · GitHub](https://github.com/TheBlueMatt/bips/blob/d46a29ff4b4ac27210bc81474ae18e4802141324/bip-XXXX.mediawiki) which has a number of advantages over the existing LN Address as well as being generic for all Bitcoin payment forms (see the rationale section for more info). By resolving DNS names to bitcoin: URIs, it is also highly extensible - any Bitcoin payment scheme that defines a bitcoin: URI query parameter doesn’t have to do anything and can support this resolution scheme (as long as they have a static invoice format, so no BOLT11). --- _[View the full topic](https://delvingbitcoin.org/t/human-readable-bitcoin-payment-instructions/542)._