From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WxByF-0003nd-It for bitcoin-development@lists.sourceforge.net; Wed, 18 Jun 2014 09:15:55 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.219.52 as permitted sender) client-ip=209.85.219.52; envelope-from=mh.in.england@gmail.com; helo=mail-oa0-f52.google.com; Received: from mail-oa0-f52.google.com ([209.85.219.52]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WxByD-0001C3-RN for bitcoin-development@lists.sourceforge.net; Wed, 18 Jun 2014 09:15:55 +0000 Received: by mail-oa0-f52.google.com with SMTP id j17so1166279oag.39 for ; Wed, 18 Jun 2014 02:15:48 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.182.181.74 with SMTP id du10mr716545obc.52.1403082948182; Wed, 18 Jun 2014 02:15:48 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.71.162 with HTTP; Wed, 18 Jun 2014 02:15:48 -0700 (PDT) In-Reply-To: <20140617155845.8177ADFC55C@quidecco.de> References: <20140617155845.8177ADFC55C@quidecco.de> Date: Wed, 18 Jun 2014 11:15:48 +0200 X-Google-Sender-Auth: 91xMFUoPGb4WfTRczcNn3X3lxRs Message-ID: From: Mike Hearn To: Isidor Zeuner Content-Type: multipart/alternative; boundary=089e0118479ab7aa0504fc18b404 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 X-Headers-End: 1WxByD-0001C3-RN Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] instant confirmation via payment protocol backwards compatible proto buffer extension 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: Wed, 18 Jun 2014 09:15:55 -0000 --089e0118479ab7aa0504fc18b404 Content-Type: text/plain; charset=UTF-8 Please, let's talk about other anti-double spend things on a separate thread. On Tue, Jun 17, 2014 at 5:58 PM, Isidor Zeuner wrote: > What prevents the following steps from happening: > I linked to Satoshi's post on this earlier, he explains why it works there, assuming people follow the original protocol rules. Your analysis holds as long as network abandons the original Bitcoin design. Obviously, we hope people won't do that. If everyone decides not to do things how Satoshi laid out then things will break, although whether we have a failure of "Bitcoin" at that point is debatable. --089e0118479ab7aa0504fc18b404 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Please, let's talk about other anti-double spend thing= s on a separate thread.

On Tue, Jun 17, 2014 at 5:58 PM, Isidor Zeuner <= cryptocur= rencies@quidecco.de> wrote:
What prevents the following steps from happe= ning:

I linked to Satoshi's post on= this earlier, he explains why it works there, assuming people follow the o= riginal protocol rules.

Your analysis holds as long as network abandons the ori= ginal Bitcoin design. Obviously, we hope people won't do that. If every= one decides not to do things how Satoshi laid out then things will break, a= lthough whether we have a failure of "Bitcoin" at that point is d= ebatable.
--089e0118479ab7aa0504fc18b404--