From d899595d041b8643a5cbfac2d2772e7768ac6deb Mon Sep 17 00:00:00 2001 From: Hugo Date: Thu, 15 Aug 2024 16:09:02 +1000 Subject: [PATCH] Adds BTC DNS scheme for Money Addresses (#40) Refers to resolving a Money Address via DNS according to BIP-0353[^0]. Changes: - Updates table of contents - Adds BTC DNS currency specific part definition Notes: - In the format definition, I've referred to the user-provided input value as `internet-identifier`, based on the address specific defined by RFC 5322[^1]. Although BIP-0353 does not explicitly mention this, its definition does match RFC 5322. [^0]: https://github.com/bitcoin/bips/blob/master/bip-0353.mediawiki [^1]: https://datatracker.ietf.org/doc/html/rfc5322#section-3.4.1 --- README.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/README.md b/README.md index fcea436..a695780 100644 --- a/README.md +++ b/README.md @@ -30,6 +30,7 @@ - [BTC Lightning Address](#btc-lightning-address) - [BTC LNURL](#btc-lnurl) - [BTC Silent Payment Address (BIP-0352)](#btc-silent-payment-address-bip-0352) + - [BTC DNS (BIP-0353)](#btc-dns-bip-0353) - [KES Mobile Money](#kes-mobile-money) - [Currency Specific Parts](#currency-specific-parts) - [USDC](#usdc) @@ -46,6 +47,8 @@ - [Format](#format-3) - [Silent Payment Address](#silent-payment-address) - [Format](#format-4) + - [DNS (BIP-353)](#dns-bip-353) + - [Format](#format-5) - [DID Resource](#did-resource) - [Examples](#examples-2) - [Example Service Entry](#example-service-entry) @@ -217,6 +220,10 @@ urn:: `urn:btc:spaddr:sp1qqweplq6ylpfrzuq6hfznzmv28djsraupudz0s0dclyt8erh70pgwxqkz2ydatksrdzf770umsntsmcjp4kcz7jqu03jeszh0gdmpjzmrf5u4zh0c` +#### BTC DNS ([BIP-0353](https://github.com/bitcoin/bips/blob/master/bip-0353.mediawiki)) + +`urn:btc:dns:hugo@hugo.md` + #### KES Mobile Money `urn:kes:momo:mpesa:254712345678` @@ -266,6 +273,11 @@ This specification proposes Currency Specific Parts for USDC and BTC. ###### Format `urn:btc:spaddr:
` +##### DNS (BIP-353) + +###### Format +`urn:btc:dns:` + ## DID Resource A Money address is associated to a DID by representing it as a [Service](https://www.w3.org/TR/did-core/#services) entry on a [DID Document](https://www.w3.org/TR/did-core/#dfn-did-documents).