From: "Luke-Jr" <luke@dashjr•org>
To: Rick Wesson <rick@support-intelligence•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] bitcoin DNS addresses
Date: Tue, 26 Jul 2011 02:18:56 -0400 [thread overview]
Message-ID: <201107260218.59313.luke@dashjr.org> (raw)
In-Reply-To: <CAJ1JLttnARz=f0UmzJKpCXpMeKg1X_R7Jfwv7tZq_pJqn8LbQQ@mail.gmail.com>
On Tuesday, July 26, 2011 12:54:23 AM Rick Wesson wrote:
> > 1. Right now you practically need a unique Bitcoin address per
> > transaction.
>
> I'd like to find ways to alievate this requirement.
Admittedly, my proposal to email a signed message allows one to reuse
addresses, but there is still a privacy concern.
> > 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.
http://www.google.com/search?q=%22PROTECT+IP+act%22+DNSSEC
> > 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.
I only meant that foo.bar.net is not the same formatting.
foo@bar•net would be.
next prev parent reply other threads:[~2011-07-26 6:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 0:29 Rick Wesson
2011-07-26 1:35 ` Matt Corallo
2011-07-26 3:35 ` Rick Wesson
2011-07-26 4:22 ` Luke-Jr
2011-07-26 4:54 ` Rick Wesson
2011-07-26 6:18 ` Luke-Jr [this message]
2011-07-26 8:04 ` John Smith
2011-07-26 13:23 ` Matt Corallo
[not found] ` <CAJ1JLtvHubiC_f_a17fnXODs54CCdmxPf8+Zz4M5X9d8VEfFSQ@mail.gmail.com>
[not found] ` <1311691885.23041.2.camel@Desktop666>
[not found] ` <CAJ1JLtsLXEPFkBuHf6ZKUSVYUnY+NL7TtsEswGvdTYtrZZTXWw@mail.gmail.com>
2011-07-26 16:24 ` Matt Corallo
2011-07-26 16:50 ` Rick Wesson
2011-07-26 17:18 ` Matt Corallo
2011-07-30 11:34 ` Mike Hearn
2011-07-30 13:42 ` Rick Wesson
2011-07-30 14:07 ` Matt Corallo
2011-07-26 16:32 phantomcircuit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201107260218.59313.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=rick@support-intelligence$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox