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
|
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 1YLvum-0001Nu-Ry
for bitcoin-development@lists.sourceforge.net;
Thu, 12 Feb 2015 15:42:52 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.173 as permitted sender)
client-ip=209.85.212.173; envelope-from=mh.in.england@gmail.com;
helo=mail-wi0-f173.google.com;
Received: from mail-wi0-f173.google.com ([209.85.212.173])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YLvuh-0001tv-BW
for bitcoin-development@lists.sourceforge.net;
Thu, 12 Feb 2015 15:42:52 +0000
Received: by mail-wi0-f173.google.com with SMTP id bs8so5296474wib.0
for <bitcoin-development@lists.sourceforge.net>;
Thu, 12 Feb 2015 07:42:41 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.194.61.145 with SMTP id p17mr8504520wjr.35.1423755761237;
Thu, 12 Feb 2015 07:42:41 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.194.188.11 with HTTP; Thu, 12 Feb 2015 07:42:41 -0800 (PST)
In-Reply-To: <CAAt2M1-L+3KEvWV+4UUSZX7meXkdTMPdz8SsxqsRtGhxsjHKmg@mail.gmail.com>
References: <20150212064719.GA6563@savin.petertodd.org>
<CANEZrP2uVT_UqJbzyQcEbiS78T68Jj2cH7OGXv5QtYiCwArDdA@mail.gmail.com>
<CAE28kUQ87jWhq1p6RK1eKEuEP1ERxN_P2SS0=YsFEGAqRyMPLA@mail.gmail.com>
<CANEZrP2H2T2QFZceCc=YzwwiApJy7kY7FN0LoAZODGbW12SYsw@mail.gmail.com>
<CAE28kURa8g3YTPi-GHKAt4v0csxXe=QhGhV3aQcDZGSr=Lb7RQ@mail.gmail.com>
<CANEZrP2hAUsRfeXUo-DLiiRmG5uJcwFuP4=o1S6Fb7ts5Ud=bw@mail.gmail.com>
<CAAt2M1-L+3KEvWV+4UUSZX7meXkdTMPdz8SsxqsRtGhxsjHKmg@mail.gmail.com>
Date: Thu, 12 Feb 2015 16:42:41 +0100
X-Google-Sender-Auth: Ml0p5UnlHaoj9k43FeZE0Ax2wIs
Message-ID: <CANEZrP2Bg=yzoc0br7u=uNnZK4TMoaBbff+0t4uP3DcRaAnW7w@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Natanael <natanael.l@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bacc0f2654a20050ee5f8e0
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: 1YLvuh-0001tv-BW
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
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: <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: Thu, 12 Feb 2015 15:42:53 -0000
--047d7bacc0f2654a20050ee5f8e0
Content-Type: text/plain; charset=UTF-8
>
> I see no fundamental difference in outcome from miner collusion in
> scorched-fee (which isn't guaranteed to pay the "right" pool!) and miner
> collusion in knowingly mining a doublespend transaction.
>
Well, they're the same thing. Replace-by-fee *is* miner collusion in
knowingly mining a double spend, just triggered in a certain way.
Remember that you aren't paying the bad pool, the bad pool is paying you.
Whichever pool benefits from the scorched earth protocol can simply pick an
address out of the transaction it perceived as starting the protocol, and
pay that.
> Zero-conf needs something else for security. A guarantee it can not be
> doublespent in the relevant time frame.
>
I think this is the core point which many of these debates revolve around.
No payment system provides *guarantees*, though some are stronger than
others. All they do is manage risk.
--047d7bacc0f2654a20050ee5f8e0
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:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><p dir=3D"ltr">I see no fundamental difference i=
n outcome from miner collusion in scorched-fee (which isn't guaranteed =
to pay the "right" pool!) and miner collusion in knowingly mining=
a doublespend transaction.</p></blockquote><div>Well, they're the same=
thing. Replace-by-fee <i>is</i>=C2=A0miner collusion in knowingly mining a=
double spend, just triggered in a certain way.</div><div><br></div><div>Re=
member that you aren't paying the bad pool, the bad pool is paying you.=
Whichever pool benefits from the scorched earth protocol can simply pick a=
n address out of the transaction it perceived as starting the protocol, and=
pay that.</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">
<p dir=3D"ltr">Zero-conf needs something else for security. A guarantee it =
can not be doublespent in the relevant time frame.<br></p>
</blockquote></div>I think this is the core point which many of these debat=
es revolve around.</div><div class=3D"gmail_extra"><br></div><div class=3D"=
gmail_extra">No payment system provides <i>guarantees</i>, though some are =
stronger than others. All they do is manage risk.</div></div>
--047d7bacc0f2654a20050ee5f8e0--
|
