summaryrefslogtreecommitdiff
path: root/23/7d3efc489d9fc30e525f32e241a4f10e241b9e
blob: 171ddb341dec6bb120c44f52f523e77e9a17daa4 (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
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 D3556259
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri,  1 Dec 2017 04:12:36 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from forward3.bravehost.com (forward3.bravehost.com [65.39.211.70])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id DAB933F4
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri,  1 Dec 2017 04:12:35 +0000 (UTC)
X-Virus-Scanned: amavisd-new at bravehost.com
Received: from [10.137.3.35] (lumumba.torservers.net [77.247.181.163])
	(Authenticated sender: cannon@cannon-ciota.info)
	by forward3.bravehost.com (Postfix) with ESMTPSA id 419D21257;
	Thu, 30 Nov 2017 20:12:31 -0800 (PST)
To: mandar mulherkar <mandar.mulherkar@gmail.com>,
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
References: <CAHneDF3qH9OUxqLthY6hEzzFr21QJFLV5wOP8jw+p5eOtpb2oQ@mail.gmail.com>
From: CANNON <cannon@cannon-ciota.info>
Message-ID: <88db7e18-e290-a81a-7f71-a9a66e564464@cannon-ciota.info>
Date: Fri, 1 Dec 2017 04:12:24 +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: <CAHneDF3qH9OUxqLthY6hEzzFr21QJFLV5wOP8jw+p5eOtpb2oQ@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:12:36 -0000

On 11/30/2017 10:20 PM, mandar mulherkar via bitcoin-dev wrote:
> Hello,
> 
> I am new, so apologies if this has been asked before.
> 
> Here are a few questions to start with -
> 
> I was wondering in terms of mass adoption, instead of long wallet
> addresses, maybe there should be a DNS-like decentralized mapping service
> to provide a user@crypto address?

Check out namecoin, there is also blockstack as someone mentioned, but I personally feel namecoin is technologically better.

If do not want a static bitcoin address mapped to a username, could use a stealth address (we need more
support for stealth addresses in bitcoin wallets).