public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Vessenes <peter@coinlab.com>
To: Jeff Garzik <jgarzik@exmulti.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Payment protocol thoughts
Date: Tue, 2 Oct 2012 15:35:05 -0700	[thread overview]
Message-ID: <CAMGNxUvLLATwbxkojOq5L+2bJc5DE=tj09x+M=EKDNpb4r-17w@mail.gmail.com> (raw)
In-Reply-To: <CA+8xBpeDo3R_fjrzUMJV-EqSkqGt1MHweYFP9TdcxDTCNtkF4g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 819 bytes --]

I meant sent twice, a.

No double-spends that I'm aware of. Sorry for the loose verbiage!

Peter

On Tue, Oct 2, 2012 at 11:07 AM, Jeff Garzik <jgarzik@exmulti.com> wrote:

> On Tue, Oct 2, 2012 at 1:52 PM, Peter Vessenes <peter@coinlab.com> wrote:
> > This is small, but an interesting tidbit from BTC Foundation payments;
> > roughly 3-5% of our initial members double-spent. WOW, that's terrible.
>
> To be specific, do you mean
>
> a) paid twice
>      or
> b) sent BF coins, then sent the same coins elsewhere
> ?
>
> Double-spend is a specific technical term....
>
> --
> Jeff Garzik
> exMULTI, Inc.
> jgarzik@exmulti.com
>



-- 
------------------------------

[image: CoinLab Logo]PETER VESSENES
CEO

*peter@coinlab.com * /  206.486.6856  / SKYPE: vessenes
811 FIRST AVENUE  /  SUITE 480  /  SEATTLE, WA 98104

[-- Attachment #2: Type: text/html, Size: 2235 bytes --]

  reply	other threads:[~2012-10-02 22:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-02 16:38 [Bitcoin-development] Payment protocol thoughts Mike Hearn
2012-10-02 17:43 ` Gavin Andresen
2012-10-02 17:52   ` Peter Vessenes
2012-10-02 18:07     ` Jeff Garzik
2012-10-02 22:35       ` Peter Vessenes [this message]
2012-10-02 22:44   ` Mike Hearn
2012-10-02 22:52     ` Gregory Maxwell

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='CAMGNxUvLLATwbxkojOq5L+2bJc5DE=tj09x+M=EKDNpb4r-17w@mail.gmail.com' \
    --to=peter@coinlab.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=jgarzik@exmulti.com \
    /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