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>
Subject: Re: [bitcoin-dev] A DNS-like decentralized mapping for wallet
 addresses?
Precedence: list


--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--