public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@bitpay.com>
To: Adam Back <adam@cypherspace.org>
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?))
Date: Fri, 18 Apr 2014 10:26:17 -0400	[thread overview]
Message-ID: <CAJHLa0Pzazg2zXGA3ZBDg3GLgoGYhP6uzy804u69s+sR3w7vMA@mail.gmail.com> (raw)
In-Reply-To: <20140416110627.GA8131@netbook.cypherspace.org>

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/



  reply	other threads:[~2014-04-18 14:26 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-16  8:14 [Bitcoin-development] Warning message when running wallet in Windows XP (or drop support?) Wladimir
2014-04-16  8:45 ` Melvin Carvalho
2014-04-16  9:41   ` Wladimir
2014-04-16 11:06     ` [Bitcoin-development] mid-term bitcoin security (Re: Warning message when running wallet in Windows XP (or drop support?)) Adam Back
2014-04-18 14:26       ` Jeff Garzik [this message]
2014-04-18 14:39       ` Justus Ranvier
2014-04-16 15:12 ` [Bitcoin-development] Warning message when running wallet in Windows XP (or drop support?) Kevin
2014-04-16 15:20   ` Pieter Wuille
2014-04-16 15:28     ` Wladimir
2014-04-16 16:27       ` Kevin
2014-04-16 16:35         ` Mark Friedenbach
2014-04-16 16:41           ` Chris Williams
2014-04-16 16:44             ` Mark Friedenbach
2014-04-16 16:50               ` Chris Williams
2014-04-16 18:59             ` Kevin
2014-04-16 19:43       ` Adam Back
2014-04-16 20:42     ` Roy Badami
2014-04-16 21:10       ` Laszlo Hanyecz
2014-04-16 21:29         ` Kevin
2014-04-16 21:39           ` Mark Friedenbach
2014-04-16 22:00             ` Pieter Wuille
2014-04-16 15:23   ` Mark Friedenbach
2014-04-16 22:06 ` Gregory Maxwell
2014-04-17  7:39   ` Wladimir
     [not found] ` <CACKnu1prEkZb5L4bGeKfjHtW+1CLmAuYr2-OWq0z5z+SvxhLTg@mail.gmail.com>
2014-04-17  7:27   ` Wladimir

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJHLa0Pzazg2zXGA3ZBDg3GLgoGYhP6uzy804u69s+sR3w7vMA@mail.gmail.com \
    --to=jgarzik@bitpay.com \
    --cc=adam@cypherspace.org \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox