Thomas Voegtlin [ARCHIVE] on Nostr: ๐
Original date posted:2015-07-20 ๐ Original message:Le 20/07/2015 17:14, Mike ...
๐
Original date posted:2015-07-20
๐ Original message:Le 20/07/2015 17:14, Mike Hearn a รฉcrit :
>
> By "alias" you mean domain name? I'm not sure what DNS key means in this
> context.
>
yes, sorry, I mean the domain name corresponding to the TXT record.
it's called 'alias' in the context of OpenAlias.
> I'm still not really convinced that a domain name under some new roots is
> an identity people will want to use, but yes, I guess your approach would
> work for those who do want it.
What do you mean by "under some new roots" ?
If I believe Netki, there is enough people who want to have a Bitcoin
address stored in DNS, for at least one company to thrive. :)
All I am proposing is a new usage for these already existing DNS
records; not only to receive BTC, but also to sign requests with them.
> It still may be worth exploring the compact cert+optimized BIP70 (no
> DNSSEC) in a qrcode if making a network that stores small bits of data
> really is beyond us :(
>
Heh, pastebin + base64 encoding the PR could work. However, it might
violate their ToS. More seriously, there might be some legal issues for
a company willing to provide that kind of service.
Re QR codes: 150 bytes, using base43 encoding, is not too bad.
Published at
2023-06-07 15:42:08Event JSON
{
"id": "1cb42d5dcd9dd62e314d9d506c82a8dfa827293ce094e8a928ceeb040dfea58f",
"pubkey": "7a4ba40070e54012212867182c66beef592603fe7c7284b72ffaafce9da20c05",
"created_at": 1686152528,
"kind": 1,
"tags": [
[
"e",
"2b792280c7c77e1a9146c50dbbc2a8f3336e57397d73b26f225d7fe35c48cd85",
"",
"root"
],
[
"e",
"8fe50e96be97bb39c4120f6f1bd73929c8cf0d82d2e282353032e8bfa196d718",
"",
"reply"
],
[
"p",
"f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2"
]
],
"content": "๐
Original date posted:2015-07-20\n๐ Original message:Le 20/07/2015 17:14, Mike Hearn a รฉcrit :\n\u003e \n\u003e By \"alias\" you mean domain name? I'm not sure what DNS key means in this\n\u003e context.\n\u003e \n\nyes, sorry, I mean the domain name corresponding to the TXT record.\nit's called 'alias' in the context of OpenAlias.\n\n\n\u003e I'm still not really convinced that a domain name under some new roots is\n\u003e an identity people will want to use, but yes, I guess your approach would\n\u003e work for those who do want it.\n\nWhat do you mean by \"under some new roots\" ?\n\nIf I believe Netki, there is enough people who want to have a Bitcoin\naddress stored in DNS, for at least one company to thrive. :)\n\nAll I am proposing is a new usage for these already existing DNS\nrecords; not only to receive BTC, but also to sign requests with them.\n\n\u003e It still may be worth exploring the compact cert+optimized BIP70 (no\n\u003e DNSSEC) in a qrcode if making a network that stores small bits of data\n\u003e really is beyond us :(\n\u003e \nHeh, pastebin + base64 encoding the PR could work. However, it might\nviolate their ToS. More seriously, there might be some legal issues for\na company willing to provide that kind of service.\n\nRe QR codes: 150 bytes, using base43 encoding, is not too bad.",
"sig": "b3bcf5dbcfbd10003a726e9997ae0576fb9ae48f3343de904d1f2fe248d70c60af340a4539bdccbbd0f76727c5d62f00ad3a170f969e1bce28aa591fdbf4ce97"
}