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
|
Return-Path: <j@toom.im>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 3EBB81073
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 7 Feb 2016 17:54:18 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id E14CF2F
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 7 Feb 2016 17:54:15 +0000 (UTC)
Received: from [192.168.1.190] (63.135.62.197.nwinternet.com [63.135.62.197]
(may be forged)) (authenticated bits=0)
by c.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id u17HsAvQ005039
(version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT);
Sun, 7 Feb 2016 09:54:11 -0800
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed;
boundary="Apple-Mail=_AE988D28-38EF-45E5-AFD1-D738F5407771";
protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5.2
From: Jonathan Toomim <j@toom.im>
In-Reply-To: <22e401d161cc$66af6b50$340e41f0$@xbt.hk>
Date: Sun, 7 Feb 2016 09:56:48 -0800
Message-Id: <7D9FA815-D816-4DFD-B96A-469C9051885F@toom.im>
References: <CABsx9T1Bd0-aQg-9uRa4u3dGA5fKxaj8-mEkxVzX8mhdj4Gt2g@mail.gmail.com> <CABm2gDoungCbB22_SKHcedBKegWEPpjeM2woxLGchC4=om8BrA@mail.gmail.com> <1804222.7gVHPiWqto@kiwi>
<201602062046.40193.luke@dashjr.org> <CABsx9T0N_TBbmy3xr-mqNDdKVF_3_QHYA1W2ttsZBQnt4dWxgw@mail.gmail.com> <20160207151927.GA14750@sapphire.erisian.com.au>
<57C403C6-2680-4C3D-8860-E33A525A99D4@toom.im>
<22e401d161cc$66af6b50$340e41f0$@xbt.hk>
To: jl2012@xbt.hk
X-Mailer: Apple Mail (2.1878.6)
X-Sonic-CAuth: UmFuZG9tSVYtCkyFrL0fP7ByzaOesUMjcSjMyL2/PJR89OgQTzKL1Xva4tEKMUbieD2N3T5O461WozvUHeRpReZPK9QUFeHa
X-Sonic-ID: C;Qo2IysPN5RGi08El14k5kQ== M;mIgOy8PN5RGi08El14k5kQ==
X-Sonic-Spam-Details: 1.2/5.0 by cerberusd
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,HTML_MESSAGE,
RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>,
Anthony Towns <aj@erisian.com.au>
Subject: Re: [bitcoin-dev] BIP proposal: Increase block size limit to 2
megabytes
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Feb 2016 17:54:18 -0000
--Apple-Mail=_AE988D28-38EF-45E5-AFD1-D738F5407771
Content-Type: multipart/alternative;
boundary="Apple-Mail=_61C52ACD-6C96-4CFD-ABBE-366FBD5B6D7E"
--Apple-Mail=_61C52ACD-6C96-4CFD-ABBE-366FBD5B6D7E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=iso-8859-1
On Feb 7, 2016, at 9:24 AM, jl2012@xbt.hk wrote:
> You are making a very na=EFve assumption that miners are just looking =
for profit for the next second. Instead, they would try to optimize =
their short term and long term ROI. It is also well known that some =
miners would mine at a loss, even not for ideological reasons, if they =
believe that their action is beneficial to the network and will provide =
long term ROI. It happened after the last halving in 2012. Without any =
immediate price appreciation, the hashing rate decreased by only less =
than 10%
>=20
In 2012, revenue dropped by about 50% instantaneously. That does not =
mean that profitability became negative.
The difficulty at the time of the halving was about 3M. The exchange =
rate was about $12. A common miner at the time was the Radeon 6970, =
which performed about 350 Mh/s on 200 W for about 1.75 Mh/J. A computer =
with 4 6970s would use about 1 kW of power, once AC/DC losses and CPU =
overhead are taken into account. This 1 kW rig would have earned about =
$0.22/kWh before the halving, and $0.11/kWh after the halving. Since =
it's not hard to find electricity cheaper than $0.11/kWh, the hashrate =
didn't drop much.
It's a common misconception that the mining hashrate increases until an =
equilibrium is reached, and nobody is making a profit any longer. =
However, this is not true. The hashrate stops increasing when the =
expected operating profit over a reasonable time frame is no longer =
greater than the hardware cost, not when the operating profit approaches =
zero. For example, an S7 right now costs a little over $1000. If I don't =
expect to earn more than $1000 in operating profit over the next year or =
two with an S7, then I won't buy one.
Right now, an S7 earns about $190/month and costs about $60/month to =
operate, for a profit of $120/month. After the halving, revenue would =
drop to $95/month (or less, depending on difficulty and exchange rate), =
leaving profit at about $35/month. The $120/month profit is good enough =
motivation to buy hardware now, and the $35/month would be good enough =
motivation to keep running hardware after the halving.
I know in advance when the halvings are coming. There's going to be one =
in about 5 months, for example. I'm going to stop buying miners before =
the halving even if they're very profitable for a month because I don't =
want to be stuck with hardware that won't reach 100% return on =
investment (ROI).
--Apple-Mail=_61C52ACD-6C96-4CFD-ABBE-366FBD5B6D7E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=iso-8859-1
<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><div><div>On Feb 7, 2016, at 9:24 AM, <a =
href=3D"mailto:jl2012@xbt.hk">jl2012@xbt.hk</a> =
wrote:</div><div><br></div><blockquote type=3D"cite"><div style=3D"margin:=
0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;"><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125);">You are making a very na=EFve =
assumption that miners are just looking for profit for the next second. =
Instead, they would try to optimize their short term and long term ROI. =
It is also well known that some miners would mine at a loss, even not =
for ideological reasons, if they believe that their action is beneficial =
to the network and will provide long term ROI. It happened after the =
last halving in 2012. Without any immediate price appreciation, the =
hashing rate decreased by only less than =
10%<o:p></o:p></span></div><div><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, =
125);"><br></span></div></blockquote></div><div><br></div><div><div><div>I=
n 2012, revenue dropped by about 50% instantaneously. That does not mean =
that profitability became =
negative. </div></div></div><div><br></div><div>The difficulty at =
the time of the halving was about 3M. The exchange rate was about $12. A =
common miner at the time was the Radeon 6970, which performed about 350 =
Mh/s on 200 W for about 1.75 Mh/J. A computer with 4 6970s would use =
about 1 kW of power, once AC/DC losses and CPU overhead are taken into =
account. This 1 kW rig would have earned about $0.22/kWh before the =
halving, and $0.11/kWh after the halving. Since it's not hard to find =
electricity cheaper than $0.11/kWh, the hashrate didn't drop =
much.</div><div><div><div><br></div></div></div><div>It's a common =
misconception that the mining hashrate increases until an equilibrium is =
reached, and nobody is making a profit any longer. However, this is not =
true. The hashrate stops increasing when the expected operating profit =
over a reasonable time frame is no longer greater than the hardware =
cost, not when the operating profit approaches zero. For example, an S7 =
right now costs a little over $1000. If I don't expect to earn more than =
$1000 in operating profit over the next year or two with an S7, then I =
won't buy one.</div><div><br></div><div>Right now, an S7 earns about =
$190/month and costs about $60/month to operate, for a profit of =
$120/month. After the halving, revenue would drop to $95/month (or less, =
depending on difficulty and exchange rate), leaving profit at about =
$35/month. The $120/month profit is good enough motivation to buy =
hardware now, and the $35/month would be good enough motivation to keep =
running hardware after the halving.</div><div><br></div>I know in =
advance when the halvings are coming. There's going to be one in =
about 5 months, for example. I'm going to stop buying miners before the =
halving even if they're very profitable for a month because I don't want =
to be stuck with hardware that won't reach 100% return on investment =
(ROI).<div><br><div><br></div></div></body></html>=
--Apple-Mail=_61C52ACD-6C96-4CFD-ABBE-366FBD5B6D7E--
--Apple-Mail=_AE988D28-38EF-45E5-AFD1-D738F5407771
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org
iQEcBAEBCgAGBQJWt4VhAAoJEIEuMk4MG0P1J48H/iv3V3tAr9nZeQozIaO01LHH
LmeVFYdjQ1Dtej7o7jrWuoNJzdzlN1QHbcalwrYZFmGLraETcONOuUriYILM1QE5
RQ8VmSdl2TbXDtlV8zIpNfZVk04cIkGZh3O3UJKR3aQXIU9MMATHQENWpp61bJIh
vHnMpS5rv4tNDj6Xt++dMVBO9smGM5ivgRvjm/IybsFmb4Q7h5dVkM3FceZD2hRD
GM4iow5doCMjz+f0qvIyHnLddnN0MFo8z7VV4PgdWmzDcjZ71V0lfhLWIC2T7gi9
p3ZKEUVpCFSa0XtpDyl4WRCgKjnOfKT8qMYWy/jvEr4q5EITJwePed4NLRiJhaw=
=AV5g
-----END PGP SIGNATURE-----
--Apple-Mail=_AE988D28-38EF-45E5-AFD1-D738F5407771--
|
