1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
|
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 <mh.in.england@gmail.com>) 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 <bitcoin-development@lists.sourceforge.net>;
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: <CAKrJrGOBSiY5V59eko6g796j3wh9V9ZLjPbyHeS5=zyX6j3Wdw@mail.gmail.com>
<CANEZrP0Euc1mPhRc9e41tU4zMDrWesvVyiBpAPq6M3m7K=aU=A@mail.gmail.com>
<CAFDyEXgKpbE4WGAqROJ4J1UST=tXWgfn7uKhRO_tngJfVK_Czw@mail.gmail.com>
<CADE3-jA8LizD8cjdqKm0pFc8OV7JqPBGhs4uvp6=VhEU2emV6w@mail.gmail.com>
<20140617155845.8177ADFC55C@quidecco.de>
Date: Wed, 18 Jun 2014 11:15:48 +0200
X-Google-Sender-Auth: 91xMFUoPGb4WfTRczcNn3X3lxRs
Message-ID: <CANEZrP2ydFvD6QnmyaJ6zQ3iUGMJAp_mcj8CXwGozkFY+njRfQ@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Isidor Zeuner <cryptocurrencies@quidecco.de>
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 <bitcoin-development@lists.sourceforge.net>
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: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=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 <cryptocurrencies@quidecco.de
> 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
<div dir=3D"ltr">Please, let's talk about other anti-double spend thing=
s on a separate thread.<div class=3D"gmail_extra"><br><div class=3D"gmail_q=
uote">On Tue, Jun 17, 2014 at 5:58 PM, Isidor Zeuner <span dir=3D"ltr"><=
<a href=3D"mailto:cryptocurrencies@quidecco.de" target=3D"_blank">cryptocur=
rencies@quidecco.de</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">What prevents the following steps from happe=
ning:<br></blockquote><div><br></div><div>I linked to Satoshi's post on=
this earlier, he explains why it works there, assuming people follow the o=
riginal protocol rules.</div>
<div><br></div><div>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.</div>
</div></div></div>
--089e0118479ab7aa0504fc18b404--
|
