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
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
|
Return-Path: <joroark@vt.edu>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id B4CB8927
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 1 Dec 2017 03:08:35 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from omr1.cc.vt.edu (outbound.smtp.vt.edu [198.82.183.121])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 92DB73CC
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 1 Dec 2017 03:08:34 +0000 (UTC)
Received: from mr3.cc.vt.edu (mr3.cc.vt.edu
[IPv6:2607:b400:92:8500:0:7f:b804:6b0a])
by omr1.cc.vt.edu (8.14.4/8.14.4) with ESMTP id vB138XmV019901
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 30 Nov 2017 22:08:33 -0500
Received: from mail-pl0-f71.google.com (mail-pl0-f71.google.com
[209.85.160.71])
by mr3.cc.vt.edu (8.14.7/8.14.7) with ESMTP id vB138SxY002047
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 30 Nov 2017 22:08:33 -0500
Received: by mail-pl0-f71.google.com with SMTP id 33so3789172pll.9
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 30 Nov 2017 19:08:33 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:subject:to:references:from:message-id:date
:user-agent:mime-version:in-reply-to;
bh=I44/3+/r4DzSKEUHzaLmOkunbjENSxcjv/2TTFo1H6o=;
b=m+hIgPIW5YkGVSMPQGmsvNcFrWURbzNg+8KT/Rk5geuuTd3gBpHdZPhs41+laEi6FB
kWA2xUuDSHjBDnVGJ2qxk8PP1sGfX9Ps1ga80ayDRlPo0F+f2/WQ00w9RMoPLhZc+Rot
2pngi0SPuabBEcqpEtIzyJXlKtCcSy7veLstVRlcr7ZY3FnF+bgFgVvrNI6lof6ZuDZR
hdwsBcxDVFzfTJ6XwD5k+R4cj1w2gfaVwBXZobJ0UvD3Nx5+XTV2qTvXBR7CSx/t+9vp
tZP0vrsjlXGqLUduhp2jPhZ2tMlqnfp5j+YwuESdxAPXf30bV2tbW1ybR0tttPqg4Le+
8tgw==
X-Gm-Message-State: AJaThX6THkAFmXa63W+t/VAqsW7dfpgczRkhs0/P6UX3d3aypF6YjBLV
c0jMpr0EjxcfWUs5VhZuKx05yDPlfoVUv2EolgH53uM9VwVeO0i9EazZVvSC9qipknn8eHRTSzH
CYEYMpUgVtKsEFUrTVxP0Ac8f8FqPk647FM7fgEat+NyrDZyT5g8OF47EAhOUPx0ll7YuRTwF/e
mTAs7QwbwgGpdHB/9d
X-Received: by 10.84.215.146 with SMTP id l18mr4682030pli.451.1512097707576;
Thu, 30 Nov 2017 19:08:27 -0800 (PST)
X-Google-Smtp-Source: AGs4zMYjPxHGcuoZdpsoh3t4ZzjaVwAcLRMTwxCpwc1aQYESkhSR/Vc1u73eu1Fq0v7Rn5LysnKsWw==
X-Received: by 10.84.215.146 with SMTP id l18mr4682003pli.451.1512097707128;
Thu, 30 Nov 2017 19:08:27 -0800 (PST)
Received: from [192.168.1.127] (c-24-22-123-27.hsd1.or.comcast.net.
[24.22.123.27]) by smtp.googlemail.com with ESMTPSA id
j3sm9005617pfh.142.2017.11.30.19.08.26
for <bitcoin-dev@lists.linuxfoundation.org>
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Thu, 30 Nov 2017 19:08:26 -0800 (PST)
To: bitcoin-dev@lists.linuxfoundation.org
References: <CAHneDF3qH9OUxqLthY6hEzzFr21QJFLV5wOP8jw+p5eOtpb2oQ@mail.gmail.com>
From: Douglas Roark <joroark@vt.edu>
Message-ID: <c889543b-8dbe-b88c-5f47-7aee1db697aa@vt.edu>
Date: Thu, 30 Nov 2017 19:08:24 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0)
Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <CAHneDF3qH9OUxqLthY6hEzzFr21QJFLV5wOP8jw+p5eOtpb2oQ@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha512;
protocol="application/pgp-signature";
boundary="MDRigl5bQP6MkITVnHgHtDR1mgINNNgoQ"
X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
T_RP_MATCHES_RCVD autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
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 03:08:35 -0000
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--MDRigl5bQP6MkITVnHgHtDR1mgINNNgoQ
Content-Type: multipart/mixed; boundary="Ar3fB0gjILEnGJFFQMCwFp6llpb30UTOx";
protected-headers="v1"
From: Douglas Roark <joroark@vt.edu>
To: bitcoin-dev@lists.linuxfoundation.org
Message-ID: <c889543b-8dbe-b88c-5f47-7aee1db697aa@vt.edu>
Subject: Re: [bitcoin-dev] A DNS-like decentralized mapping for wallet
addresses?
References: <CAHneDF3qH9OUxqLthY6hEzzFr21QJFLV5wOP8jw+p5eOtpb2oQ@mail.gmail.com>
In-Reply-To: <CAHneDF3qH9OUxqLthY6hEzzFr21QJFLV5wOP8jw+p5eOtpb2oQ@mail.gmail.com>
--Ar3fB0gjILEnGJFFQMCwFp6llpb30UTOx
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
On 2017/11/30 14:20, mandar mulherkar via bitcoin-dev wrote:
> 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?
A few years ago, I was part of an effort with Armory and Verisign to
make something similar to what you're describing.
https://tools.ietf.org/html/draft-wiley-paymentassoc-00 is where you can
find the one and only official draft. I worked on a follow-up with some
changes and some nice appendices, explaining some nice tricks one could
use to make payment management flexible. For various reasons, it never
got published. I think it's an interesting draft that could be turned
into something useful. Among other things, it was able to leverage BIP32
and allow payment requests to be generated that automatically pointed
payees to the correct branch. DNSSEC may have some issues but, AFAIK,
it's as the easiest way to bootstrap identity to a common, reasonably
secure standard.
--=20
---
Douglas Roark
Cryptocurrency, network security, travel, and art.
https://onename.com/droark
joroark@vt.edu
PGP key ID: 26623924
--Ar3fB0gjILEnGJFFQMCwFp6llpb30UTOx--
--MDRigl5bQP6MkITVnHgHtDR1mgINNNgoQ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org
iQJDBAEBCgAtFiEEbTFwwdwsb9Cu68pnQ4EdGiZiOSQFAlogx6kPHGpvcm9hcmtA
dnQuZWR1AAoJEEOBHRomYjkkMBYQAJmhUpb4d0wqqH6itaFOroXzWzKgNA+47dKv
eA5J/Eal9Tk/HRnpK5kP2cqtCF+NYsBISm7KFjGwD3EnVEIv8Z972ZE+D93WCm6G
8OqXtHdohZdxoVnkPpXZMCC6RlC2cc4RpquosYeWu2MIsAKrD+S8THdkdEO+wFbw
V5KryQQBJqy0tFfEvMFnWV3EpxSC+iX6ZSZGCtu6ExtJa0aXt0Z99AoNmb2ZGCJD
xumXd3gr1LiK2EyqqXfSGqHA6wDDkIKm+rUzMbCGcJf980jXYfmScrcwEqWictfR
ow48MbuOt1al8ZbeCYEp2jMlFKXwKxTXBXsfTLjhdZG0llHaYvYaZ/o2ERtb4jdi
RNRf01RlBUgDTMQksgTFd4MS2Kn1pp+juQqjCLA6k8ibfFF4VDhOFc07/SapC/We
9Db62eOO+2gSQEhV7FCUQRgQfYuTUVArSHAL+bizxY/hppOneQMhvfzNaJhtq7Ak
6mqJbwhtofXYSi56yUSaHA2qe15dkWazP+GLr+ze5FoXfZj9NTvZrKgWBr/nh1Hb
s9jg/ys5ZIS3m7VE5JbjSTNoGh47FX+dOqoVHYQrB16Ft5OfSJmUCrVXPIZLjjdI
pUj9V5vjM7y6A+ivxx5Mvn7oz4cw/wljpQJmCmM1WaCsNg0A+aKiXyOn6ZHyrVBl
gm6ZTi+A
=VHv3
-----END PGP SIGNATURE-----
--MDRigl5bQP6MkITVnHgHtDR1mgINNNgoQ--
|
