summaryrefslogtreecommitdiff
path: root/bc/2abc86d43d56610dba1fe887babfa8fe0a07ab
blob: 5ef593933b2f26d956233f1849a6d4436e018f53 (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
Return-Path: <cannon@cannon-ciota.info>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id DD1017A8
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri,  1 Dec 2017 04:17:49 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from forward2.bravehost.com (forward2.bravehost.com [65.39.211.66])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 9C8A0EB
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri,  1 Dec 2017 04:17:49 +0000 (UTC)
X-Virus-Scanned: amavisd-new at bravehost.com
Received: from [10.137.3.35] (tor-exit-readme.memcpy.io [163.172.67.180])
	(Authenticated sender: cannon@cannon-ciota.info)
	by forward2.bravehost.com (Postfix) with ESMTPSA id AFA611FBA;
	Thu, 30 Nov 2017 20:17:46 -0800 (PST)
To: Lucas Clemente Vella <lvella@gmail.com>,
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
	mandar mulherkar <mandar.mulherkar@gmail.com>
References: <CAHneDF3qH9OUxqLthY6hEzzFr21QJFLV5wOP8jw+p5eOtpb2oQ@mail.gmail.com>
	<CAGCathwjmj_f0TWZF=BhdCq=dSZ_R53Frd3A9b2SgFtus-AH=g@mail.gmail.com>
From: CANNON <cannon@cannon-ciota.info>
Message-ID: <143c8bc4-77a7-a097-fbc1-75a1210e60ca@cannon-ciota.info>
Date: Fri, 1 Dec 2017 04:17:37 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
	Icedove/45.6.0
MIME-Version: 1.0
In-Reply-To: <CAGCathwjmj_f0TWZF=BhdCq=dSZ_R53Frd3A9b2SgFtus-AH=g@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW
	autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
X-Mailman-Approved-At: Sat, 02 Dec 2017 11:16:38 +0000
Subject: Re: [bitcoin-dev] A DNS-like decentralized mapping for wallet
 addresses?
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Dec 2017 04:17:50 -0000

On 12/01/2017 03:15 AM, Lucas Clemente Vella via bitcoin-dev wrote:
> Unfortunately it didn't catch, but it would

Interesting, I just mentioned namecoin literally seconds before this email arrived.
Saying "it did not catch" is not accurate I'd say. It still works great, and namecoin
has actually made great progress this year 2017. I'd say that namecoin has great potential
but just not widely adopted yet.

Would be real nice to have namecion support in major bitcoin wallets for name to data mapping.