Rick Wesson [ARCHIVE] on Nostr: 📅 Original date posted:2011-07-26 🗒️ Summary of this message: Proposal to ...
📅 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. ;)
>
🗒️ 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. ;)
>