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
154
155
156
157
158
159
160
|
Return-Path: <sjors@sprovoost.nl>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id D91CB8E3
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 18 Dec 2017 11:26:22 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com
[66.111.4.27])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 23FE6171
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 18 Dec 2017 11:26:22 +0000 (UTC)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
by mailout.nyi.internal (Postfix) with ESMTP id 28AFC2108D;
Mon, 18 Dec 2017 06:26:21 -0500 (EST)
Received: from frontend1 ([10.202.2.160])
by compute1.internal (MEProxy); Mon, 18 Dec 2017 06:26:21 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sprovoost.nl; h=
content-type:date:from:in-reply-to:message-id:mime-version
:references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=
fm1; bh=RGE1kIQwon+e2OnVyoZ52dohy1r76AlZsTZc4rYggC4=; b=OKvKXN+2
6+vJxEf/G+2fAd0hydxZ8V+4PUoSsxtg1NHPF+cffR9UoBiJ9OB1ivyesxOgUd3t
6xIWHsV4m6r7PzmUeoFnoFxaowvRwtUK9fe3o5TIIni5Dmrrbt/Lt+9nrXgSkM7z
WJzCTytRgoxvMFaNk5IgG5+zCVs4818kZWyCQ2tHaJMI6uVGjOusGmPdDZBMu2/5
kn7/ey7OCZFRvCYwoGVPqeN45tW88NJ9To6USHhguXemSRad7PEiICqU+BJQpBEU
3da+GW2VXzyY1UfkcGvf1JcM8EqxvM53FnLFh/VuxK4xaE89SVuP5DAmINTZ2kLy
YL6oug4jNUAffw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
messagingengine.com; h=content-type:date:from:in-reply-to
:message-id:mime-version:references:subject:to:x-me-sender
:x-me-sender:x-sasl-enc; s=fm1; bh=RGE1kIQwon+e2OnVyoZ52dohy1r76
AlZsTZc4rYggC4=; b=Gm6iN9wRvg/J7d/bPdch/4BwKsR/oKx9nv/8AOKjIuvFZ
JNx370OgeX6ZJpOiKnLFu2wAym350PM7VfwkssVOIe/w7SQ0Kpr9oHNb59C/supT
k31lnHCiYPkwpCxl7TdnSZkfO9Xbqb6+kv+A+gmOb2077kkCvVir+QqTm4uFKG4Y
mXg+FHdk/7wBAeUQXeFxb0POoFGmUzlbP1e7c0E39Nr76TIQeRQYCO7edNM8g6jY
cjSpDusHFpk/cLL8h3n+V8/ThnajpUzKx3qyR/tr7VkRawtuVkBCS3KC8vP68cfX
SiJfLzGbNOs04v6Pu/Butbg41Q0lp7j00IxCl2j0w==
X-ME-Sender: <xms:3aU3WqW_83QAZOlpc3Tp5PyhyepUPc6LLn45lRXY_FDGNAKz6nPdGQ>
Received: from [10.46.107.158] (unknown [212.123.217.146])
by mail.messagingengine.com (Postfix) with ESMTPA id 9F8197E4C8;
Mon, 18 Dec 2017 06:26:20 -0500 (EST)
From: Sjors Provoost <sjors@sprovoost.nl>
Content-Type: multipart/signed;
boundary="Apple-Mail=_77CF1115-B045-4FEC-AFD0-47DD9A17C004";
protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Mon, 18 Dec 2017 12:26:19 +0100
References: <CAHneDF3qH9OUxqLthY6hEzzFr21QJFLV5wOP8jw+p5eOtpb2oQ@mail.gmail.com>
<c889543b-8dbe-b88c-5f47-7aee1db697aa@vt.edu>
To: Douglas Roark <joroark@vt.edu>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
In-Reply-To: <c889543b-8dbe-b88c-5f47-7aee1db697aa@vt.edu>
Message-Id: <1085B203-DB5E-42AB-A9F3-467D09246314@sprovoost.nl>
X-Mailer: Apple Mail (2.3445.5.20)
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, 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: Mon, 18 Dec 2017 11:54:24 +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: Mon, 18 Dec 2017 11:26:23 -0000
--Apple-Mail=_77CF1115-B045-4FEC-AFD0-47DD9A17C004
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=us-ascii
Have you thought about combining this with BIP-47? You could associate =
payment codes with email via DNS.
It would be nice if there was a way to get rid of the announcement =
transaction in BIP-47 and establish a shared secret out of bound. That =
would simplify things, at the cost of an additional burden of storing =
more than an HD seed to recover a wallet that received funds this way.
Perhaps the sender can email to the recipient the information they need =
to retrieve the funds. The (first) transaction could have a time locked =
refund in it, in case the payment code is stale.
Sjors
> Op 1 dec. 2017, om 04:08 heeft Douglas Roark via bitcoin-dev =
<bitcoin-dev@lists.linuxfoundation.org> het volgende geschreven:
>=20
> 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?
>=20
> 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
>=20
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
--Apple-Mail=_77CF1115-B045-4FEC-AFD0-47DD9A17C004
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE7ZvfetalXiMuhFJCV/+b28wwEAkFAlo3pdsACgkQV/+b28ww
EAlozhAAmpIyQKQEf1Wuigb6FMMqkXb0FTLW4UMzZSLvwvxikcaQLwpoc+cI7ewb
0Wsp9/ryEZ/N8Me0pT9hlelcl1JMDRETkfBog0rp5Gt1aH30YVRmJqOOC8vSqIYu
62UZjmoAF850yydM+rKHG7TMvJIkNKtpBI5P/xz154gpJGO7qD+k6xNggZ75jiho
aklh96cqjWJZQwZtcXvEfw/C+0IIRVQUBPIvK8alPYhNw2PpkrjgOv8Z2RrIoN4U
sYq3erLuQPU8Wra0qqREKel3oIXKVXhHOHzn8UNBJ1WTp4ME60JtNaQwJtcwJnx7
4lAfQnHhtYw+BXAspS1JfpkmIGEnTKtIEOI3PqKKh0E68w3/pDGbIx5w4+JbsKP5
cfKIvO5xmIi0HV0yYbJrXvpHy+13xQnvvKopa7jK+MqMGZGw3O2iIFDKAheFU78d
O6rMTAgqsFVQys7G1j8gwENvq1ZGjzlXbSp2n/EMTV7qaPIZcZe97W44N4iPEi6S
yaoH0yqMckcrkQfrNS0Wl9+d3k5WROgaxp+X9ybA8PvcWJeGFticV5KE8O2zW0v7
Hq4vvjE2rTNho8GOoilgq56FwX8HvIl+YZaQanp7VVtm7BBqnDkHY4JCX4R/LJlx
8acucAB/gOT0mGQ8X+qtMvswf8GZXHHfZXSIdfQbo60mnYX+KzA=
=AcV5
-----END PGP SIGNATURE-----
--Apple-Mail=_77CF1115-B045-4FEC-AFD0-47DD9A17C004--
|
