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
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1Z63dc-0003R1-L6
for bitcoin-development@lists.sourceforge.net;
Fri, 19 Jun 2015 21:15:48 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bitpay.com
designates 209.85.218.50 as permitted sender)
client-ip=209.85.218.50; envelope-from=jgarzik@bitpay.com;
helo=mail-oi0-f50.google.com;
Received: from mail-oi0-f50.google.com ([209.85.218.50])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Z63db-00087j-KK
for bitcoin-development@lists.sourceforge.net;
Fri, 19 Jun 2015 21:15:48 +0000
Received: by oiyy130 with SMTP id y130so71528148oiy.0
for <bitcoin-development@lists.sourceforge.net>;
Fri, 19 Jun 2015 14:15:42 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc:content-type;
bh=mcZJlrutze6x0rjaGUv1FZSS18rbbvS7NpVphJv6Xig=;
b=HSySH5lISHyhNnYJJDG6kWxX9x/5iZqb4vHvsXXaVFs39gQDixXZNKCXXZ9Gq5aPi6
Oo2j22JDGGMge9DFlDGNkRBT7tdOpQ+KLI0rU6OxuUtMMIWvdM3hJ9g1cfqVYNn/JZ8R
pImy3Yi5nAqRHEcrwhDqFowWULCkmHaOIeDxg6seDO1hAIwfFvadqjcSdRjLvxeUwD+1
G2OO7QxOLu+gvAv+6uhjwxeXIdUtmyle7XdB2hHVouXDpL5rgUshQ7kfnq+w03HIEpc3
+m8A9jTK9XI34ZISgfic2qB68QxE7jtFLfWgBRuFSqJrCgl3+q73NldpU8NmUwRl5Fku
X/Aw==
X-Gm-Message-State: ALoCoQkg0b583yakJ8bh1LhDVccQvfj1pamvIZq5Ufe4fKkPTzqMJJE7KQC2b5DTMVbj839vIbeY
X-Received: by 10.202.74.10 with SMTP id x10mr14359693oia.98.1434748542058;
Fri, 19 Jun 2015 14:15:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.108.149 with HTTP; Fri, 19 Jun 2015 14:15:21 -0700 (PDT)
In-Reply-To: <CALxyHsVKUJtskOtnqS4_R0U=vwLhVzC+0i6Ya0QyT8T644dYHA@mail.gmail.com>
References: <20150619103959.GA32315@savin.petertodd.org>
<20150619154054.GA13498@savin.petertodd.org>
<CAMK47c84w=2c9y8MKHTzFf05DmKXz74a=iFViA-oZ1uRDZCAWg@mail.gmail.com>
<6716121.uS5ifrNBZv@crushinator>
<CALxyHsVKUJtskOtnqS4_R0U=vwLhVzC+0i6Ya0QyT8T644dYHA@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Fri, 19 Jun 2015 14:15:21 -0700
Message-ID: <CAJHLa0NAwCodhWvbFCtejVZiwiUsC5BKd7iZzAggqYgH-CxZTA@mail.gmail.com>
To: Frank Flores <frankf44@gmail.com>
Content-Type: multipart/alternative; boundary=001a1134fa14311ad90518e56d6c
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 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
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.1 AWL AWL: Adjusted score from AWL reputation of From: address
X-Headers-End: 1Z63db-00087j-KK
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] F2Pool has enabled full replace-by-fee
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: Fri, 19 Jun 2015 21:15:48 -0000
--001a1134fa14311ad90518e56d6c
Content-Type: text/plain; charset=UTF-8
Double spend detection is by definition best-effort.
The purpose of bitcoin is to provide security (confirmations) to otherwise
insecure, possibly double spent transactions.
On Fri, Jun 19, 2015 at 2:05 PM, Frank Flores <frankf44@gmail.com> wrote:
> Has anyone from Mycelium weighed in on this? Is their doublespend attack
> detection broken with this kind of irresponsible behavior?
>
> On Fri, Jun 19, 2015 at 3:39 PM, Matt Whitlock <bip@mattwhitlock.name>
> wrote:
>
>> On Friday, 19 June 2015, at 9:18 am, Adrian Macneil wrote:
>> > If full-RBF sees any significant adoption by miners, then it will
>> actively
>> > harm bitcoin adoption by reducing or removing the ability for online or
>> POS
>> > merchants to accept bitcoin payments at all.
>>
>> Retail POS merchants probably should not be accepting vanilla Bitcoin
>> payments, as Bitcoin alone does not (and cannot) guarantee the
>> irreversibility of a transaction until it has been buried several blocks
>> deep in the chain. Retail merchants should be requiring a co-signature from
>> a mutually trusted co-signer that vows never to sign a double-spend. The
>> reason we don't yet see such technology permeating the ecosystem is
>> because, to date, zero-conf transactions have been irreversible "enough,"
>> but this has only been a happy accident; it was never promised, and it
>> should not be relied upon.
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
>
>
>
> --
> *MONEY IS OVER!*
> IF YOU WANT IT
> <http://www.zeitgeistmovie.com/>
> =====================================================
> The causes of my servitude can be traced to the tyranny of money.
> -Serj Tankian
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
--001a1134fa14311ad90518e56d6c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Double spend detection is by definition best-effort.<div><=
br></div><div>The purpose of bitcoin is to provide security (confirmations)=
to otherwise insecure, possibly double spent transactions.</div><div><br><=
/div><div><br><div><br></div></div></div><div class=3D"gmail_extra"><br><di=
v class=3D"gmail_quote">On Fri, Jun 19, 2015 at 2:05 PM, Frank Flores <span=
dir=3D"ltr"><<a href=3D"mailto:frankf44@gmail.com" target=3D"_blank">fr=
ankf44@gmail.com</a>></span> wrote:<br><blockquote class=3D"gmail_quote"=
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><d=
iv dir=3D"ltr">Has anyone from Mycelium weighed in on this? Is their double=
spend attack detection broken with this kind of irresponsible behavior?</di=
v><div class=3D"gmail_extra"><div><div class=3D"h5"><br><div class=3D"gmail=
_quote">On Fri, Jun 19, 2015 at 3:39 PM, Matt Whitlock <span dir=3D"ltr">&l=
t;<a href=3D"mailto:bip@mattwhitlock.name" target=3D"_blank">bip@mattwhitlo=
ck.name</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Friday, =
19 June 2015, at 9:18 am, Adrian Macneil wrote:<br>
> If full-RBF sees any significant adoption by miners, then it will acti=
vely<br>
> harm bitcoin adoption by reducing or removing the ability for online o=
r POS<br>
> merchants to accept bitcoin payments at all.<br>
<br>
Retail POS merchants probably should not be accepting vanilla Bitcoin payme=
nts, as Bitcoin alone does not (and cannot) guarantee the irreversibility o=
f a transaction until it has been buried several blocks deep in the chain. =
Retail merchants should be requiring a co-signature from a mutually trusted=
co-signer that vows never to sign a double-spend. The reason we don't =
yet see such technology permeating the ecosystem is because, to date, zero-=
conf transactions have been irreversible "enough," but this has o=
nly been a happy accident; it was never promised, and it should not be reli=
ed upon.<br>
<div><div><br>
---------------------------------------------------------------------------=
---<br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net" target=3D"_bla=
nk">Bitcoin-development@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" rel=3D"noreferrer" target=3D"_blank">https://lists.sourceforge.net/lists/=
listinfo/bitcoin-development</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div></div><=
/div><span class=3D"HOEnZb"><font color=3D"#888888">-- <br><div><div style=
=3D"text-align:left"><b><span style=3D"font-size:xx-large">MONEY IS OVER!</=
span></b></div><div><div style=3D"text-align:left"><span style=3D"font-size=
:x-small">=C2=A0=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"http://www.z=
eitgeistmovie.com/" target=3D"_blank">IF YOU WANT IT</a></span></div>=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D<br>The causes of my servitude can be traced to the tyranny of money.<br=
>-Serj Tankian</div></div>
</font></span></div>
<br>-----------------------------------------------------------------------=
-------<br>
<br>_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" rel=3D"noreferrer" target=3D"_blank">https://lists.sourceforge.net/lists/=
listinfo/bitcoin-development</a><br>
<br></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div cla=
ss=3D"gmail_signature">Jeff Garzik<br>Bitcoin core developer and open sourc=
e evangelist<br>BitPay, Inc. =C2=A0 =C2=A0 =C2=A0<a href=3D"https://bitpay.=
com/" target=3D"_blank">https://bitpay.com/</a></div>
</div>
--001a1134fa14311ad90518e56d6c--
|
