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 ) id 1YMEWV-0004xe-Uq for bitcoin-development@lists.sourceforge.net; Fri, 13 Feb 2015 11:35:03 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.212.180 as permitted sender) client-ip=209.85.212.180; envelope-from=mh.in.england@gmail.com; helo=mail-wi0-f180.google.com; Received: from mail-wi0-f180.google.com ([209.85.212.180]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YMEWU-0004cf-E6 for bitcoin-development@lists.sourceforge.net; Fri, 13 Feb 2015 11:35:03 +0000 Received: by mail-wi0-f180.google.com with SMTP id h11so11371626wiw.1 for ; Fri, 13 Feb 2015 03:34:56 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.194.121.168 with SMTP id ll8mr4594338wjb.35.1423827296385; Fri, 13 Feb 2015 03:34:56 -0800 (PST) Sender: mh.in.england@gmail.com Received: by 10.194.188.11 with HTTP; Fri, 13 Feb 2015 03:34:56 -0800 (PST) In-Reply-To: References: <20150212064719.GA6563@savin.petertodd.org> Date: Fri, 13 Feb 2015 12:34:56 +0100 X-Google-Sender-Auth: E3ky86NGjPXFX1bAaaLJsrKGW-4 Message-ID: From: Mike Hearn To: Gregory Maxwell Content-Type: multipart/alternative; boundary=089e01227e9e390110050ef6a0ef X-Spam-Score: -0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.0 AWL AWL: Adjusted score from AWL reputation of From: address X-Headers-End: 1YMEWU-0004cf-E6 Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] replace-by-fee v0.10.0rc4 X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2015 11:35:04 -0000 --089e01227e9e390110050ef6a0ef Content-Type: text/plain; charset=UTF-8 > > > history. Lots of miners have dropped out due to hardware obsolescence, > yet > > massive double spending hasn't happened. > > How many thousands of BTC must be stolen by miners before you'd agree > that it has, in fact, happened? > (https://bitcointalk.org/index.php?topic=321630.0) > Hmm. I think this is a disagreement over the term massive. I was meaning we don't see double spending like we see carding fraud in the traditional online payments world. We can talk about Finney attacks by linking to specific discussions of specific events, because they are very rare, which is why merchants generally ignore the possibility. I didn't mean the numeric value of lost coins added up so far. --089e01227e9e390110050ef6a0ef Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
> history. Lots of miners ha= ve dropped out due to hardware obsolescence, yet
> massive double spending hasn't happened.

How many thousands of BTC must be stolen by miners before you'd = agree
that it has, in fact, happened?
(https://bitcointalk.org/index.php?topic=3D321630.0)

Hmm. I think this is a disagreement over the term m= assive. I was meaning we don't see double spending like we see carding = fraud in the traditional online payments world. We can talk about Finney at= tacks by linking to specific discussions of specific events, because they a= re very rare, which is why merchants generally ignore the possibility. I di= dn't mean the numeric value of lost coins added up so far.
<= /div>
--089e01227e9e390110050ef6a0ef--