diff options
author | Peter Todd <pete@petertodd.org> | 2014-01-16 16:28:05 -0500 |
---|---|---|
committer | bitcoindev <bitcoindev@gnusha.org> | 2014-01-16 21:28:20 +0000 |
commit | a11a2e509fcbfca5627845f3772f1c38742f0479 (patch) | |
tree | 24ecf161028bbe9b578b3fb6e744869b0c52eb2f | |
parent | cda1920d019d9fe2a37ddb548494306f9e035bc7 (diff) | |
download | pi-bitcoindev-a11a2e509fcbfca5627845f3772f1c38742f0479.tar.gz pi-bitcoindev-a11a2e509fcbfca5627845f3772f1c38742f0479.zip |
Re: [Bitcoin-development] Stealth Addresses
-rw-r--r-- | 68/c5df358210e057939d8797fe25432cd75005bb | 160 |
1 files changed, 160 insertions, 0 deletions
diff --git a/68/c5df358210e057939d8797fe25432cd75005bb b/68/c5df358210e057939d8797fe25432cd75005bb new file mode 100644 index 000000000..4621d9ecc --- /dev/null +++ b/68/c5df358210e057939d8797fe25432cd75005bb @@ -0,0 +1,160 @@ +Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] + helo=mx.sourceforge.net) + by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <pete@petertodd.org>) id 1W3uU8-0003zu-Pq + for bitcoin-development@lists.sourceforge.net; + Thu, 16 Jan 2014 21:28:20 +0000 +Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of petertodd.org + designates 62.13.148.161 as permitted sender) + client-ip=62.13.148.161; envelope-from=pete@petertodd.org; + helo=outmail148161.authsmtp.com; +Received: from outmail148161.authsmtp.com ([62.13.148.161]) + by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76) + id 1W3uU5-0008V8-L5 for bitcoin-development@lists.sourceforge.net; + Thu, 16 Jan 2014 21:28:20 +0000 +Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235]) + by punt15.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s0GLSAbG083117; + Thu, 16 Jan 2014 21:28:10 GMT +Received: from petertodd.org (petertodd.org [174.129.28.249]) + (authenticated bits=128) + by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s0GLS5rw032703 + (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); + Thu, 16 Jan 2014 21:28:08 GMT +Date: Thu, 16 Jan 2014 16:28:05 -0500 +From: Peter Todd <pete@petertodd.org> +To: Jeremy Spilman <jeremy@taplink.co> +Message-ID: <20140116212805.GA4421@petertodd.org> +References: <CAAS2fgTz0TaGhym_35V3N2-vHVzU9BeuV8q+QJjwh5bg77FEZg@mail.gmail.com> + <CANEZrP0huBWqgvQik9Yc26Tu4CwR0VSXcfC+qfzsZqvoU4VJGA@mail.gmail.com> + <20140113133746.GI38964@giles.gnomon.org.uk> + <CANEZrP1KAVhi_-cxCYe0rR9LUSYJ8MyW8=6eSJZ65FeY5ZJNuQ@mail.gmail.com> + <20140114225321.GT38964@giles.gnomon.org.uk> + <CANAnSg0tH_bK_19rsRRHOeZgrGYeWMhW89fXPyS4DQGmS4r_7A@mail.gmail.com> + <CALimQCXgc0eXeOcqFGUaCpSF7gKEe87KzvLqHZwUysV3WyjjGw@mail.gmail.com> + <CAAS2fgShChAQryfUOBp60jB-zxn2tH986fu1HfT+LsNdBYnoYg@mail.gmail.com> + <CAJHLa0P5r2+kxy7w8G=h=TAhdk1jUoW5UOiv-euo47uQY0u9ZA@mail.gmail.com> + <op.w9q6jdsayldrnw@laptop-air.hsd1.ca.comcast.net> +MIME-Version: 1.0 +Content-Type: multipart/signed; micalg=pgp-sha256; + protocol="application/pgp-signature"; boundary="fUYQa+Pmc3FrFX/N" +Content-Disposition: inline +In-Reply-To: <op.w9q6jdsayldrnw@laptop-air.hsd1.ca.comcast.net> +User-Agent: Mutt/1.5.21 (2010-09-15) +X-Server-Quench: 181067f0-7ef5-11e3-b802-002590a15da7 +X-AuthReport-Spam: If SPAM / abuse - report it at: + http://www.authsmtp.com/abuse +X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR + bgdMdwQUElQaAgsB AmIbWVVeUlV7WWs7 ag1VcwRfa1RMVxto + VEFWR1pVCwQmQhx2 en0bEF5ydAdBeH0+ Z0JrWHUVXUx7dUB6 + FE5JEjhQYHphaTUc TRJQdwFJcANIexZF O1F6ACIKLwdSbGoL + NQ4vNDcwO3BTJTpY RgYVKF8UXXNDJSIx ThQeHX0GEUEfSj4o IgdO +X-Authentic-SMTP: 61633532353630.1023:706 +X-AuthFastPath: 0 (Was 255) +X-AuthSMTP-Origin: 174.129.28.249/587 +X-AuthVirus-Status: No virus detected - but ensure you scan with your own + anti-virus system. +X-Spam-Score: -1.5 (-) +X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. + See http://spamassassin.org/tag/ for more details. + -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for + sender-domain + -0.0 SPF_PASS SPF: sender matches SPF record +X-Headers-End: 1W3uU5-0008V8-L5 +Cc: "bitcoin-development@lists.sourceforge.net" + <bitcoin-development@lists.sourceforge.net> +Subject: Re: [Bitcoin-development] Stealth Addresses +X-BeenThere: bitcoin-development@lists.sourceforge.net +X-Mailman-Version: 2.1.9 +Precedence: list +List-Id: <bitcoin-development.lists.sourceforge.net> +List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> +List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> +List-Post: <mailto:bitcoin-development@lists.sourceforge.net> +List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> +List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> +X-List-Received-Date: Thu, 16 Jan 2014 21:28:21 -0000 + + +--fUYQa+Pmc3FrFX/N +Content-Type: text/plain; charset=us-ascii +Content-Disposition: inline +Content-Transfer-Encoding: quoted-printable + +On Wed, Jan 15, 2014 at 04:05:27PM -0800, Jeremy Spilman wrote: +> Might I propose "reusable address". +>=20 +> I think that describes it best to any non-programmer, and even more +> so encourages wallets to present options as 'one time use' vs +> 'reusable'. +>=20 +> It definitely packs a marketing punch which could help drive +> adoption. The feature is only useful if/when broadly adopted. + +I'm very against the name "reusable addresses" and strongly belive we +should stick with the name stealth addresses. + +You gotta look at it from the perspective of a user; lets take standard +pay-to-pubkey-hash addresses: I can tell my wallet to pay one as many +times as I want and everything works just great. I also can enter the +address on blockchain.info's search box, and every transaction related +to the address, and the balance of it, pops up immediately. + +What is that telling me? A: Addresses starting with "1" are reusable. B: +Transactions associated with them appear to be public knowledge. + +Now I upgrade my wallet software and it says I now have a "reusable" +address. My reaction is "Huh? Normal addresses are reusable, what's +special about this weird reusable address thing that my buddy Bob's +wallet software couldn't pay." I might even try to enter in a "reusable" +address in blockchain.info, which won't work, and I'll just figure +"must be some new unsupported thing" and move on with my life. + +On the other hand, suppose my wallet says I now have "stealth address" +support. I'm going to think "Huh, stealth? I guess that means privacy +right? I like privacy." If I try searching for a stealth address on +blockchain.info, when it doesn't work I might think twig on "Oh right! +It said stealth addresses are private, so maybe the transactions are +hidden?" I might also think "Maybe this is like stealth/incognito mode +in my browser? So like, there's no history being kept for others to +see?" Regardless, I'm going to be thinking "well I hear scary stuff +about Bitcoin privacy, and this stealth thing sounds like it's gonna +help, so I should learn more about that" + +Finally keep in mind that stealth addresses have had a tonne of very +fast, and very wide reaching PR. The name is in the public conciousness +already, and trying to change it now just because of vague bad +associations is going to throw away the momentum of that good PR and +slow down adoption. Last night I was at the Toronto Bitcoin Meetup and I +based on conversations there with people there, technical and +non-technical, almost everyone had heard about them and almost everyone +seemed to understand the basic idea of why they were a good thing. That +just wouldn't have happened with a name that tried to hide what stealth +addresses were for, and by changing the name now we risk people not +making the connection when wallet software gets upgraded to support +them. + +--=20 +'peter'[:-1]@petertodd.org +0000000000000001b0e0ae7ef97681ad77188030b6c791aef304947e6f524740 + +--fUYQa+Pmc3FrFX/N +Content-Type: application/pgp-signature; name="signature.asc" +Content-Description: Digital signature + +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.11 (GNU/Linux) + +iQEcBAEBCAAGBQJS2E7lAAoJEBmcgzuo5/CF91kH/0nFkrXudWxKX8UgwNbPf1l5 +dqPJjoOex0esCBmY8WlmSgxUwwSjvMrQaxf/MdG71HI65oNHBTw5OM9WMBQkGFO1 +QIF9sLzTmLgShKcNPhK8adUBqSE9FQan9pljlq9l8TEHFeX9ImePh8bnw1difd0n +oSmn0LMB87gkDMuno5lp1b0C3OCMml+aOfxLZivvMmVYWGbPMEK0iuP1hRUrxFzC +yqfZWprfnk5IeXVVhK67tVJ4Dgtl0tOFej8H0J81KCOocn/4v7Et01KCjt4XBMtv +mDm2gxBnIDHUlkz3mu+REQOGt2T+gPxEYfLdIac5BA/cJatNFrlwp7UBwFBO1hU= +=pyzi +-----END PGP SIGNATURE----- + +--fUYQa+Pmc3FrFX/N-- + + |