From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) 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 ; 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> <201112121841.39864.luke@dashjr.org> <1323736946.58149.YahooMailNeo@web121001.mail.ne1.yahoo.com> <4EEB81B9.5090201@dot-bit.org> Date: Fri, 16 Dec 2011 12:48:33 -0500 Message-ID: From: Gregory Maxwell To: Khalahan 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2011 17:48:39 -0000 On Fri, Dec 16, 2011 at 12:36 PM, Khalahan 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).