📅 Original date posted:2011-07-26
🗒️ Summary of this message: Proposal to alleviate the need for unique Bitcoin addresses per transaction by using a SRV lookup and HTTPS request for Bitcoin address resolution.
📝 Original message:>
> 1. Right now you practically need a unique Bitcoin address per transaction.
I'd like to find ways to alievate this requirement.
> 2. DNSSEC is on the edge of becoming illegal in the US.
really, pointers please. DHS was a huge funder for DNSSEC asn .mil was
the first domain to deploy it. I think you may be miss-informed.
> 3. Emails aren't merely domains.
correct, I was speaking about an "address" that used the same/simular
formatting but did not use the SMTP protocol.
-rick
> I would propose something like resolving foo at bar.net to a SRV lookup for
> _bitcoinaddressresolution._tcp.foo.bar.net, expecting a cert for bar.net,
> making a HTTPS request for /bitcoinaddressresolution?foo at bar.net, and also
> sending an email to foo at bar.net (the usual way) signed with the keys used for
> the transaction. ;)
>
Rick Wesson [ARCHIVE] /
npub1xz…2925u
2023-06-07 02:07:27
in reply to nevent1q…pr99
Author Public Key
npub1xz8q68hmzur6c6uje593nscy3q4njx05h4vnxmz2wxxptx7u7casl2925uPublished at
2023-06-07 02:07:27Event JSON
{
"id": "834aee16c96628c158236c00ce06af379f9ec79f1ea1a48f477854668374791b",
"pubkey": "308e0d1efb1707ac6b92cd0b19c304882b3919f4bd59336c4a718c159bdcf63b",
"created_at": 1686103647,
"kind": 1,
"tags": [
[
"e",
"8fd54e24bd93fd7d9d848a64b03950f07049907bb67ea5380cfd81c7de7d119c",
"",
"root"
],
[
"e",
"eec161ec29ec9f8574977621ee3342c66389c26255fd1f6821ee96065030cee4",
"",
"reply"
],
[
"p",
"6ac6a519b554d8ff726a301e3daec0b489f443793778feccc6ea7a536f7354f1"
]
],
"content": "📅 Original date posted:2011-07-26\n🗒️ Summary of this message: Proposal to alleviate the need for unique Bitcoin addresses per transaction by using a SRV lookup and HTTPS request for Bitcoin address resolution.\n📝 Original message:\u003e\n\u003e 1. Right now you practically need a unique Bitcoin address per transaction.\n\nI'd like to find ways to alievate this requirement.\n\n\u003e 2. DNSSEC is on the edge of becoming illegal in the US.\n\nreally, pointers please. DHS was a huge funder for DNSSEC asn .mil was\nthe first domain to deploy it. I think you may be miss-informed.\n\n\u003e 3. Emails aren't merely domains.\n\ncorrect, I was speaking about an \"address\" that used the same/simular\nformatting but did not use the SMTP protocol.\n\n-rick\n\n\u003e I would propose something like resolving foo at bar.net to a SRV lookup for\n\u003e _bitcoinaddressresolution._tcp.foo.bar.net, expecting a cert for bar.net,\n\u003e making a HTTPS request for /bitcoinaddressresolution?foo at bar.net, and also\n\u003e sending an email to foo at bar.net (the usual way) signed with the keys used for\n\u003e the transaction. ;)\n\u003e",
"sig": "de46aedfcc8c998399e26f564c77064788228bbc71a467facc56454253a3962fad1131accf3c4f968c0f930a434c04910cac62287a0e381ce527596006c48e1e"
}