blob: d8cd1329834c66b6dedc811bcd16a883edc97929 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <rick.wesson@iidf.org>) id 1Rb01w-0007KM-8y
for bitcoin-development@lists.sourceforge.net;
Thu, 15 Dec 2011 01:22:40 +0000
X-ACL-Warn:
Received: from mail-vx0-f175.google.com ([209.85.220.175])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Rb01s-0000n1-8N
for bitcoin-development@lists.sourceforge.net;
Thu, 15 Dec 2011 01:22:40 +0000
Received: by vcbf1 with SMTP id f1so153423vcb.34
for <bitcoin-development@lists.sourceforge.net>;
Wed, 14 Dec 2011 17:22:30 -0800 (PST)
MIME-Version: 1.0
Received: by 10.52.173.197 with SMTP id bm5mr1103895vdc.7.1323912150789; Wed,
14 Dec 2011 17:22:30 -0800 (PST)
Received: by 10.52.37.80 with HTTP; Wed, 14 Dec 2011 17:22:30 -0800 (PST)
In-Reply-To: <201112141827.36100.luke@dashjr.org>
References: <1323731781.42953.YahooMailClassic@web120920.mail.ne1.yahoo.com>
<CAGQP0AE7Pd5HLmTizJVzdBLXx+mR2NwJPM6eMfUf8i=4DFL76g@mail.gmail.com>
<CAJ1JLttapMPTp0KE=V6Y5DFonvp5-dYK7KS6MoqUL8O1kt1stg@mail.gmail.com>
<201112141827.36100.luke@dashjr.org>
Date: Wed, 14 Dec 2011 17:22:30 -0800
Message-ID: <CAJ1JLtuxTmbBZsZQjKZU6zdDKx96JKTbdzuoQ=+S2h81qA9mhQ@mail.gmail.com>
From: Rick Wesson <rick@support-intelligence.com>
To: Luke-Jr <luke@dashjr.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1Rb01s-0000n1-8N
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Fwd: [BIP 15] Aliases
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 15 Dec 2011 01:22:40 -0000
understand that not *everyone* wants or will adhere to that best
practice and in my NSHO it isn't.
-rick
2011/12/14 Luke-Jr <luke@dashjr.org>:
> On Wednesday, December 14, 2011 6:02:25 PM Rick Wesson wrote:
>> I also am largely in favor of using secured zones to publish TXT
>> records to digital currencies. I've been thinking mainly about TXT
>> using the following format for bitcoin.
>>
>> _btc.<lhs>.<rhs>
>
> Don't confuse BTC (Bitcoin unit) with BC (Bitcoin in general / protocol)...
> The hard part of using DNS will be sticking to the standard good practice of
> using a new address for every transaction.
|
