Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of bitpay.com
	designates 209.85.212.169 as permitted sender)
	client-ip=209.85.212.169; envelope-from=jgarzik@bitpay.com;
	helo=mail-wi0-f169.google.com; 
MIME-Version: 1.0
In-Reply-To: <20140416110627.GA8131@netbook.cypherspace.org>
References: <CA+s+GJDdENtqQt1f+L5htuuyPxUxsq0prLQFBLirTjJz0nG1gw@mail.gmail.com>
	<CAKaEYhKDDCSOiygnfsMpO-dQKjwHnm0icoH9+oGqo+114_9sAQ@mail.gmail.com>
	<CA+s+GJB6aThjpMOUodK2Uc-jw=x6rSuRyX5gqsS+mK=DxJ7N5g@mail.gmail.com>
	<20140416110627.GA8131@netbook.cypherspace.org>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Fri, 18 Apr 2014 10:26:17 -0400
Message-ID: <CAJHLa0Pzazg2zXGA3ZBDg3GLgoGYhP6uzy804u69s+sR3w7vMA@mail.gmail.com>
To: Adam Back <adam@cypherspace.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] mid-term bitcoin security (Re: Warning
 message when running wallet in Windows XP (or drop support?))
Precedence: list

On Wed, Apr 16, 2014 at 7:06 AM, Adam Back <adam@cypherspace.org> wrote:
> Btw not to reignite the stealth vs reusable address bike shedding, but
> contrarily I was thinking it maybe actually better to try to rebrand address
> as "invoice number".  People understand double paying an invoice is not a
> good idea.  And if they receive the same invoice twice they'll query it.

And that is certainly how BitPay works today, including the language used.

-- 
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc.      https://bitpay.com/