📅 Original date posted:2015-07-23
📝 Original message:Le 17/07/2015 03:01, Justin Newton via bitcoin-dev a écrit :
>> 3> We use a 2 tier lookup format. [...]
>>
>> We do the same thing, except in a single call. [...]
>
> We looked at doing this in a single lookup as you did. With one or two
> currencies this can be potentially more efficient. As the number of
> supported currencies and addresses under a single name grows, however, this
> solution becomes potentially more problematic. [...]
Hi Justin,
Your lookup solution is indeed more efficient than OpenAlias, and more
robust to DoS. However, that is not because you use a two-tier lookup.
Indeed, instead of having the following records:
_wallet.sample = "btc ltc"
_btc._wallet.sample = "mybitcoinadress"
you could simply have:
_wallet.sample = "btc ltc"
_btc.sample = "mybitcoinaddress"
In practice, a wallet supporting only Bitcoin will skip the currencies
lookup in both cases, and go directly for the _btc record.
One benefit of having an intermediate "_wallet" level is to allow zone
delegation. Is that the reason for that choice?
Thomas
Thomas Voegtlin [ARCHIVE] /
npub10f…7ej47
2023-06-07 15:42:13
in reply to nevent1q…6kr7
Author Public Key
npub10f96gqrsu4qpygfgvuvzce47aavjvql703egfde0l2hua8dzpszs67ej47Published at
2023-06-07 15:42:13Event JSON
{
"id": "5137f53c632c2f9e546e572acc202ab4a557c101b453b3de849edeafce7d15e2",
"pubkey": "7a4ba40070e54012212867182c66beef592603fe7c7284b72ffaafce9da20c05",
"created_at": 1686152533,
"kind": 1,
"tags": [
[
"e",
"2b792280c7c77e1a9146c50dbbc2a8f3336e57397d73b26f225d7fe35c48cd85",
"",
"root"
],
[
"e",
"7128d5a87440bbe51f55b5f413fe72313481ef34d569f07bf3cdc46244ab25f3",
"",
"reply"
],
[
"p",
"2a007275f8708d857e3fc6523dad0fcbe5c6a5a1f53043352053a1048838b0d7"
]
],
"content": "📅 Original date posted:2015-07-23\n📝 Original message:Le 17/07/2015 03:01, Justin Newton via bitcoin-dev a écrit :\n\u003e\u003e 3\u003e We use a 2 tier lookup format. [...]\n\u003e\u003e\n\u003e\u003e We do the same thing, except in a single call. [...]\n\u003e \n\u003e We looked at doing this in a single lookup as you did. With one or two\n\u003e currencies this can be potentially more efficient. As the number of\n\u003e supported currencies and addresses under a single name grows, however, this\n\u003e solution becomes potentially more problematic. [...]\n\nHi Justin,\n\nYour lookup solution is indeed more efficient than OpenAlias, and more\nrobust to DoS. However, that is not because you use a two-tier lookup.\n\nIndeed, instead of having the following records:\n_wallet.sample = \"btc ltc\"\n_btc._wallet.sample = \"mybitcoinadress\"\n\nyou could simply have:\n_wallet.sample = \"btc ltc\"\n_btc.sample = \"mybitcoinaddress\"\n\nIn practice, a wallet supporting only Bitcoin will skip the currencies\nlookup in both cases, and go directly for the _btc record.\n\nOne benefit of having an intermediate \"_wallet\" level is to allow zone\ndelegation. Is that the reason for that choice?\n\nThomas",
"sig": "e1dc29384930ee607c6762c29e3dd4997d279c53c047aab0801b1b7da87b3a99a0e7c595da44ebd14e70e01011ba7f76d179288cef1a59001fd8242c9debe911"
}