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
109
110
111
112
113
114
115
116
117
118
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1WwaI0-000381-K4
for bitcoin-development@lists.sourceforge.net;
Mon, 16 Jun 2014 17:01:48 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.170 as permitted sender)
client-ip=209.85.214.170; envelope-from=mh.in.england@gmail.com;
helo=mail-ob0-f170.google.com;
Received: from mail-ob0-f170.google.com ([209.85.214.170])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WwaHy-0004ES-J3
for bitcoin-development@lists.sourceforge.net;
Mon, 16 Jun 2014 17:01:48 +0000
Received: by mail-ob0-f170.google.com with SMTP id uz6so6132780obc.1
for <bitcoin-development@lists.sourceforge.net>;
Mon, 16 Jun 2014 10:01:41 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.63.205 with SMTP id i13mr21269632oes.8.1402938101047;
Mon, 16 Jun 2014 10:01:41 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.71.162 with HTTP; Mon, 16 Jun 2014 10:01:40 -0700 (PDT)
In-Reply-To: <loom.20140616T184930-521@post.gmane.org>
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>
<CANEZrP3KKSkD7_R0Dvt600b7vh0oia78vHhPrPqSGBbwf9DsSQ@mail.gmail.com>
<loom.20140616T181739-326@post.gmane.org>
<CANEZrP3er1NVoAiVmROTxQ3TC80r7enKaHkWjOYTbKehf7qJjQ@mail.gmail.com>
<loom.20140616T184930-521@post.gmane.org>
Date: Mon, 16 Jun 2014 19:01:40 +0200
X-Google-Sender-Auth: -pvBIhMbSG6ssfuvG1xQxr1sKG4
Message-ID: <CANEZrP2fg9k9fC+QAO2GQS7VC-JCtbEjubHB9j1TJtR9vuaDSQ@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Lawrence Nahum <lawrence@greenaddress.it>
Content-Type: multipart/alternative; boundary=001a11c1d89a27ac5e04fbf6fbfe
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: 1WwaHy-0004ES-J3
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: Mon, 16 Jun 2014 17:01:48 -0000
--001a11c1d89a27ac5e04fbf6fbfe
Content-Type: text/plain; charset=UTF-8
>
> I only meant that double spends minutes apart are possible and that by then
> the sole use of a monitor is too late even if it will tell you.
>
As long as miners stick to Satoshi's first seen rule, which is the default,
it's useful:
https://bitcointalk.org/index.php?topic=423.msg3819#msg3819
(this is the famous "snack machine" thread from 2010)
If they decide to change to something like highest-fee-always-wins, then
they (again) centralise things by forcing all instant transactions to pay
GreenAddress and its competitors money - much though I like your product
Lawrence, let's hope they don't collectively lemming us all off a cliff by
doing that ;)
--001a11c1d89a27ac5e04fbf6fbfe
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;paddi=
ng-left:1ex">
I only meant that double spends minutes apart are possible and that by then=
<br>
the sole use of a monitor is too late even if it will tell you.<br></blockq=
uote><div></div></div><br></div><div class=3D"gmail_extra">As long as miner=
s stick to Satoshi's first seen rule, which is the default, it's us=
eful:</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><a href=3D"=
https://bitcointalk.org/index.php?topic=3D423.msg3819#msg3819">https://bitc=
ointalk.org/index.php?topic=3D423.msg3819#msg3819</a><br></div><div class=
=3D"gmail_extra">
<br></div><div class=3D"gmail_extra">(this is the famous "snack machin=
e" thread from 2010)</div><div class=3D"gmail_extra"><br></div><div cl=
ass=3D"gmail_extra">If they decide to change to something like highest-fee-=
always-wins, then they (again) centralise things by forcing all instant tra=
nsactions to pay GreenAddress and its competitors money - much though I lik=
e your product Lawrence, let's hope they don't collectively lemming=
us all off a cliff by doing that ;)</div>
</div>
--001a11c1d89a27ac5e04fbf6fbfe--
|
