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

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