From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id B4CB8927 for ; 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 ; 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 ; 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 ; Thu, 30 Nov 2017 22:08:33 -0500 Received: by mail-pl0-f71.google.com with SMTP id 33so3789172pll.9 for ; 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 (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: From: Douglas Roark Message-ID: 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: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 To: bitcoin-dev@lists.linuxfoundation.org Message-ID: Subject: Re: [bitcoin-dev] A DNS-like decentralized mapping for wallet addresses? References: In-Reply-To: --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--