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 8AB7C405 for ; Mon, 20 Jul 2015 15:34:09 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from relay4-d.mail.gandi.net (relay4-d.mail.gandi.net [217.70.183.196]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 7E185212 for ; Mon, 20 Jul 2015 15:34:08 +0000 (UTC) Received: from mfilter20-d.gandi.net (mfilter20-d.gandi.net [217.70.178.148]) by relay4-d.mail.gandi.net (Postfix) with ESMTP id 593CF1721B4 for ; Mon, 20 Jul 2015 17:34:06 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter20-d.gandi.net Received: from relay4-d.mail.gandi.net ([217.70.183.196]) by mfilter20-d.gandi.net (mfilter20-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id 2DFD2X+Zw20d for ; Mon, 20 Jul 2015 17:34:05 +0200 (CEST) X-Originating-IP: 85.181.106.214 Received: from [192.168.1.2] (x55b56ad6.dyn.telefonica.de [85.181.106.214]) (Authenticated sender: thomasv@electrum.org) by relay4-d.mail.gandi.net (Postfix) with ESMTPSA id E685A1721B3 for ; Mon, 20 Jul 2015 17:34:04 +0200 (CEST) Message-ID: <55AD14EC.7040603@electrum.org> Date: Mon, 20 Jul 2015 17:34:04 +0200 From: Thomas Voegtlin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 CC: bitcoin-dev@lists.linuxfoundation.org References: <55A4AF62.4090607@electrum.org> <55AB8785.4080201@electrum.org> <55AD0669.4040002@electrum.org> <55AD0B43.4010207@electrum.org> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.6 required=5.0 tests=BAYES_00,MISSING_HEADERS, RCVD_IN_DNSWL_LOW autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Subject: Re: [bitcoin-dev] Proposal: extend bip70 with OpenAlias X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jul 2015 15:34:09 -0000 Le 20/07/2015 17:14, Mike Hearn a =C3=A9crit : >=20 > By "alias" you mean domain name? I'm not sure what DNS key means in thi= s > context. >=20 yes, sorry, I mean the domain name corresponding to the TXT record. it's called 'alias' in the context of OpenAlias. > I'm still not really convinced that a domain name under some new roots = is > an identity people will want to use, but yes, I guess your approach wou= ld > work for those who do want it. What do you mean by "under some new roots" ? If I believe Netki, there is enough people who want to have a Bitcoin address stored in DNS, for at least one company to thrive. :) All I am proposing is a new usage for these already existing DNS records; not only to receive BTC, but also to sign requests with them. > It still may be worth exploring the compact cert+optimized BIP70 (no > DNSSEC) in a qrcode if making a network that stores small bits of data > really is beyond us :( >=20 Heh, pastebin + base64 encoding the PR could work. However, it might violate their ToS. More seriously, there might be some legal issues for a company willing to provide that kind of service. Re QR codes: 150 bytes, using base43 encoding, is not too bad.