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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
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 1YLtfQ-0000mL-6j
for bitcoin-development@lists.sourceforge.net;
Thu, 12 Feb 2015 13:18:52 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.178 as permitted sender)
client-ip=74.125.82.178; envelope-from=mh.in.england@gmail.com;
helo=mail-we0-f178.google.com;
Received: from mail-we0-f178.google.com ([74.125.82.178])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YLtfP-0002uJ-1F
for bitcoin-development@lists.sourceforge.net;
Thu, 12 Feb 2015 13:18:52 +0000
Received: by mail-we0-f178.google.com with SMTP id w62so9952152wes.9
for <bitcoin-development@lists.sourceforge.net>;
Thu, 12 Feb 2015 05:18:45 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.194.61.145 with SMTP id p17mr7275240wjr.35.1423747124544;
Thu, 12 Feb 2015 05:18:44 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.194.188.11 with HTTP; Thu, 12 Feb 2015 05:18:44 -0800 (PST)
In-Reply-To: <CAE28kUQ87jWhq1p6RK1eKEuEP1ERxN_P2SS0=YsFEGAqRyMPLA@mail.gmail.com>
References: <20150212064719.GA6563@savin.petertodd.org>
<CANEZrP2uVT_UqJbzyQcEbiS78T68Jj2cH7OGXv5QtYiCwArDdA@mail.gmail.com>
<CAE28kUQ87jWhq1p6RK1eKEuEP1ERxN_P2SS0=YsFEGAqRyMPLA@mail.gmail.com>
Date: Thu, 12 Feb 2015 14:18:44 +0100
X-Google-Sender-Auth: 6ES4EUsTQ1J_771pUpgudBz-q1c
Message-ID: <CANEZrP2H2T2QFZceCc=YzwwiApJy7kY7FN0LoAZODGbW12SYsw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Alex Mizrahi <alex.mizrahi@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bacc0f29bcda9050ee3f5c3
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: 1YLtfP-0002uJ-1F
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 13:18:52 -0000
--047d7bacc0f29bcda9050ee3f5c3
Content-Type: text/plain; charset=UTF-8
>
> But, let's say, 5 years from now, some faction of miners who own
> soon-to-be-obsolete equipment will decide to boost their profits with a
> replace-by-fee pool and a corresponding wallet. They can market it as "1 of
> 10 hamburgers are free" if they have 10% of the total hashpower.
>
Yes, like any P2P network Bitcoin cannot work if a sufficiently large
number of miners decide to attack it. This is an ancient argument. It came
up the moment Bitcoin was first invented.
But this argument could have been made at any time in Bitcoin's entire
history. Lots of miners have dropped out due to hardware obsolescence, yet
massive double spending hasn't happened. Perhaps the system is not as
simple as you boil it down to be.
Anyway, what would happen in that event is within a few days some people
would stop selling Bitcoin for hamburgers, others would find workarounds,
and the fees collected from the double spends would be worth very little.
Nobody wins.
So would you take a responsibility for pushing the approach which isn't
> game-theoretically sound?
>
"The approach" is how Bitcoin has always worked.
People have been using game theory to predict the imminent demise of
Bitcoin since I first found it. Just one example: "Bitcoin will collapse
when the 50->25 BTC drop happens" was promoted as a dead cert thing by game
theorists. Every miner becomes unprofitable and stops at once!
So far game theory based predictions tend to be proven wrong by reality, so
this sort of argument doesn't impress me much.
Anyway, going around this loop again is pointless. I brought up the counter
argument so people who see this thread don't mistakenly think Peter's
position is some kind of de-facto consensus about how Bitcoin should work.
Not because I love rehashing the same arguments every six months ad nauseum.
--047d7bacc0f29bcda9050ee3f5c3
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"><div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmai=
l_quote"><div>But, let's say, 5 years from now, some faction of miners =
who own soon-to-be-obsolete equipment will decide to boost their profits wi=
th a replace-by-fee pool and a corresponding wallet. They can market it as =
"1 of 10 hamburgers are free" if they have 10% of the total hashp=
ower.</div></div></div></div></blockquote><div><br></div><div>Yes, like any=
P2P network Bitcoin cannot work if a sufficiently large number of miners d=
ecide to attack it. This is an ancient argument. It came up the moment Bitc=
oin was first invented.</div><div><br></div><div>But this argument could ha=
ve been made at any time in Bitcoin's entire history. Lots of miners ha=
ve dropped out due to hardware obsolescence, yet massive double spending ha=
sn't happened. Perhaps the system is not as simple as you boil it down =
to be.</div><div><br></div><div>Anyway, what would happen in that event is =
within a few days some people would stop selling Bitcoin for hamburgers, ot=
hers would find workarounds, and the fees collected from the double spends =
would be worth very little. Nobody wins.</div><div><br></div><blockquote cl=
ass=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;padding-left:1e=
x"><div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><=
div>So would you take a responsibility for pushing the approach which isn&#=
39;t game-theoretically sound?</div></div></div></div></blockquote><div><br=
></div><div>"The approach" is how Bitcoin has always worked.</div=
><div><br></div><div>People have been using game theory to predict the immi=
nent demise of Bitcoin since I first found it. Just one example: =C2=A0 &qu=
ot;Bitcoin will collapse when the 50->25 BTC drop happens" was prom=
oted as a dead cert thing by game theorists. Every miner becomes unprofitab=
le and stops at once!<br></div><div><br></div><div>So far game theory based=
predictions tend to be proven wrong by reality, so this sort of argument d=
oesn't impress me much.</div><div><br></div><div>Anyway, going around t=
his loop again is pointless. I brought up the counter argument so people wh=
o see this thread don't mistakenly think Peter's position is some k=
ind of de-facto consensus about how Bitcoin should work. Not because I love=
rehashing the same arguments every six months ad nauseum.</div></div></div=
></div>
--047d7bacc0f29bcda9050ee3f5c3--
|
