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
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gmaxwell@gmail.com>) id 1Rbbtf-0004yZ-Rx
for bitcoin-development@lists.sourceforge.net;
Fri, 16 Dec 2011 17:48:39 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.47 as permitted sender)
client-ip=209.85.212.47; envelope-from=gmaxwell@gmail.com;
helo=mail-vw0-f47.google.com;
Received: from mail-vw0-f47.google.com ([209.85.212.47])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Rbbtf-0000Sr-0c
for bitcoin-development@lists.sourceforge.net;
Fri, 16 Dec 2011 17:48:39 +0000
Received: by vbbfc21 with SMTP id fc21so3739937vbb.34
for <bitcoin-development@lists.sourceforge.net>;
Fri, 16 Dec 2011 09:48:33 -0800 (PST)
MIME-Version: 1.0
Received: by 10.52.99.231 with SMTP id et7mr6835353vdb.114.1324057713625; Fri,
16 Dec 2011 09:48:33 -0800 (PST)
Received: by 10.220.4.68 with HTTP; Fri, 16 Dec 2011 09:48:33 -0800 (PST)
In-Reply-To: <4EEB81B9.5090201@dot-bit.org>
References: <1323731781.42953.YahooMailClassic@web120920.mail.ne1.yahoo.com>
<CAGQP0AGvq603oshSGiP79A+gqDqW_hHG+qZjaZccCmo+gd3W2A@mail.gmail.com>
<201112121841.39864.luke@dashjr.org>
<CAGQP0AGBKKEqhaJZj-Rw400AjrVHE9_EMve=RWdqoaOaDsTgtw@mail.gmail.com>
<CAGQP0AGY32QP=rXyGftb5NbHA7fhcCne7W=pt5+onXp1Jbm98Q@mail.gmail.com>
<1323736946.58149.YahooMailNeo@web121001.mail.ne1.yahoo.com>
<CANEZrP1oPaqAT+LCfrAXO9WBz+oC2uvbP=5vx2+DX2P0qFusgA@mail.gmail.com>
<CALxbBHUgCOVMRxtnsmC2W-MaYfeDSzaftWMCCgcWsMBdZfzPQg@mail.gmail.com>
<CAGQP0AHRaaB6UC5Y-mW=K6BqrzTOj9saKJjo50ZzvTpZKntnww@mail.gmail.com>
<CABsx9T1wksXjLy=EC6dK1WtVFEayL-HgXWtENgSPXhU6Du2Srg@mail.gmail.com>
<4EEB81B9.5090201@dot-bit.org>
Date: Fri, 16 Dec 2011 12:48:33 -0500
Message-ID: <CAAS2fgTxk1UWDju+GbKFfA7+U+_pq5wDCXV8mnqgcn99iEOLuQ@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Khalahan <khal@dot-bit.org>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.3 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(gmaxwell[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
0.3 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1Rbbtf-0000Sr-0c
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: Fri, 16 Dec 2011 17:48:39 -0000
On Fri, Dec 16, 2011 at 12:36 PM, Khalahan <khal@dot-bit.org> wrote:
> Namecoin is a peer-to-peer generic name/value datastore system.
> Don't forget it's not limited to .bit usage ! So, directly mapping
> things to .bit url would not be the optimal way of using namecoin.
>
> Namecoin is specificaly designed to map things to names in a fully
> decentralized way. So, it's the perfect starting point to map names to
> other things (a public bitcoin address, an url, etc)
> You won't have all the advantages of namecoin when using other systems
> like DNS and HTTP(S) as the first entry point.
How can one construct a zero-trust (or nearly zero trust) namecoin
resolver without having a copy of the ever growing complete namecoin
block chain?
The bitcoin lite node mechanism will not work because a peer could
return stale records or no-result and you would have no evidence of
their deception. (In the case of lite bitcoin nodes, telling you
about old transactions is harmless because you control your own
transactions).
|
