📅 Original date posted:2015-07-23
📝 Original message:Le 23/07/2015 11:48, Thomas Voegtlin via bitcoin-dev a écrit :
>
> One benefit of having an intermediate "_wallet" level is to allow zone
> delegation. Is that the reason for that choice?
>
Thinking about it, I think that it would be better to separate those two
operations: on one hand, the listing of TXT records under a name, and on
the other hand, the possibility to use Zone Delegation.
For example, let us use the "_oa2" name (Openalias version 2) when we
need to introduce an intermediate level, and "_oa2_keys" for key listing.
Here is an example:
_oa2_keys.sample 3600 IN TXT "btc ltc email fullname"
_btc.sample 3600 IN TXT "bitcoinaddress"
_ltc.sample 3600 IN TXT "litecoinaddress"
_btc.sample 3600 IN TXT "otherbitcoinaddress"
_email.sample 3600 IN TXT "john.smith at googlemail.com"
_fullname.sample 3600 IN TXT "John Smith"
Zone Delegation: Let us assume example.com wants to delegate all its
Bitcoin aliases to Netki. We introduce an intermediate level, with the
"_oa2" name. In the alias, this string is translated as "@"
john._oa2.example.com <-- will be looked up as john at example.com
_btc.john._oa2.example.com <-- bitcoin address of john at example.com
Thomas Voegtlin [ARCHIVE] /
npub10f…7ej47
2023-06-07 15:42:14
in reply to nevent1q…e642
Author Public Key
npub10f96gqrsu4qpygfgvuvzce47aavjvql703egfde0l2hua8dzpszs67ej47Published at
2023-06-07 15:42:14Event JSON
{
"id": "7d0f54161af178d4485647f30e32283e88086f88625f912f1c4c0c79a99409ff",
"pubkey": "7a4ba40070e54012212867182c66beef592603fe7c7284b72ffaafce9da20c05",
"created_at": 1686152534,
"kind": 1,
"tags": [
[
"e",
"2b792280c7c77e1a9146c50dbbc2a8f3336e57397d73b26f225d7fe35c48cd85",
"",
"root"
],
[
"e",
"5137f53c632c2f9e546e572acc202ab4a557c101b453b3de849edeafce7d15e2",
"",
"reply"
],
[
"p",
"7a4ba40070e54012212867182c66beef592603fe7c7284b72ffaafce9da20c05"
]
],
"content": "📅 Original date posted:2015-07-23\n📝 Original message:Le 23/07/2015 11:48, Thomas Voegtlin via bitcoin-dev a écrit :\n\u003e \n\u003e One benefit of having an intermediate \"_wallet\" level is to allow zone\n\u003e delegation. Is that the reason for that choice?\n\u003e \n\nThinking about it, I think that it would be better to separate those two\noperations: on one hand, the listing of TXT records under a name, and on\nthe other hand, the possibility to use Zone Delegation.\n\nFor example, let us use the \"_oa2\" name (Openalias version 2) when we\nneed to introduce an intermediate level, and \"_oa2_keys\" for key listing.\n\nHere is an example:\n\n_oa2_keys.sample 3600 IN TXT \"btc ltc email fullname\"\n_btc.sample 3600 IN TXT \"bitcoinaddress\"\n_ltc.sample 3600 IN TXT \"litecoinaddress\"\n_btc.sample 3600 IN TXT \"otherbitcoinaddress\"\n_email.sample 3600 IN TXT \"john.smith at googlemail.com\"\n_fullname.sample 3600 IN TXT \"John Smith\"\n\nZone Delegation: Let us assume example.com wants to delegate all its\nBitcoin aliases to Netki. We introduce an intermediate level, with the\n\"_oa2\" name. In the alias, this string is translated as \"@\"\n\njohn._oa2.example.com \u003c-- will be looked up as john at example.com\n_btc.john._oa2.example.com \u003c-- bitcoin address of john at example.com",
"sig": "4747babdff8e535e66fbacb6e007a157b3973d3b8e7d6322c79c5691b6c128481e0472807c39f17dcab9099f4b0ee95a3dc45ea99060ede31a0ea8be873dea32"
}