summaryrefslogtreecommitdiff
path: root/31/ecf314399b940f0e1eed10dba25d0c74a5890e
blob: 7f65207d5ed39c060693c5d7c3c975f1fb16154c (plain)
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
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 <alex.mizrahi@gmail.com>) id 1Xi8Hh-00037A-6O
	for bitcoin-development@lists.sourceforge.net;
	Sat, 25 Oct 2014 20:50:01 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.214.175 as permitted sender)
	client-ip=209.85.214.175; envelope-from=alex.mizrahi@gmail.com;
	helo=mail-ob0-f175.google.com; 
Received: from mail-ob0-f175.google.com ([209.85.214.175])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Xi8Hf-0002M2-RW
	for bitcoin-development@lists.sourceforge.net;
	Sat, 25 Oct 2014 20:50:01 +0000
Received: by mail-ob0-f175.google.com with SMTP id wm4so430888obc.34
	for <bitcoin-development@lists.sourceforge.net>;
	Sat, 25 Oct 2014 13:49:54 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.132.102 with SMTP id ot6mr2743854oeb.62.1414270194369;
	Sat, 25 Oct 2014 13:49:54 -0700 (PDT)
Received: by 10.202.168.142 with HTTP; Sat, 25 Oct 2014 13:49:54 -0700 (PDT)
In-Reply-To: <2109053.EM3JWxoz5A@coldstorage>
References: <CAE28kUS-uDbd_Br3H5BxwRm1PZFpOwLhcyyZT9b1_VfRaBC9jw@mail.gmail.com>
	<2109053.EM3JWxoz5A@coldstorage>
Date: Sat, 25 Oct 2014 23:49:54 +0300
Message-ID: <CAE28kUT-Ywo=de94HVJCmLJhWnf_=v5Vo=M9pjed-YhEAu5Sjw@mail.gmail.com>
From: Alex Mizrahi <alex.mizrahi@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=047d7b4721e08d49e20506457057
X-Spam-Score: -0.6 (/)
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
	(alex.mizrahi[at]gmail.com)
	-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
X-Headers-End: 1Xi8Hf-0002M2-RW
Subject: Re: [Bitcoin-development] death by halving
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: Sat, 25 Oct 2014 20:50:01 -0000

--047d7b4721e08d49e20506457057
Content-Type: text/plain; charset=UTF-8

> For the sake of argument, lets assume that somehow (quite unlikely)


Why is it unlikely? Do you believe that the cost of electricity cannot be
higher than expected mining revenue?
Or do you expect miners to keep mining when it costs them money?


> half the mining equipment gets shut off.
> The amount of hashes/second is such that it is currently, lets just say,
> quite
> secure against any takeover.
>

The equipment won't be simply turned off, it will be up for grabs.

Please check this web sites:

https://nicehash.com/
https://www.multipool.us/

One can use them in the same way he uses normal mining pools, and they
switch between different chains.
Say, multipool.us can switch between BTC and PPC (Peercoin).
Mining BTC will be less profitable after a halving, so a miner who is
willing to maximize his profits might use multipool to auto-switch to
something more profitable.
Which might be attack-on-Bitcoin.
E.g. if 60% of bitcoin's total hashrate is available via "multipools", one
can try to pull of a double-spending attack.


> Your document makes a long series of assumptions about how this can turn
> out
> bad with each individually is implausible, together are just fiction.
>

It sounds like you failed to grasp even basics.

--047d7b4721e08d49e20506457057
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"><div=
>=C2=A0</div><blockquote 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;padding-left:1ex">For the sake of argument, lets assume that so=
mehow (quite unlikely)</blockquote><div><br></div><div>Why is it unlikely? =
Do you believe that the cost of electricity cannot be higher than expected =
mining revenue?</div><div>Or do you expect miners to keep mining when it co=
sts them money?</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(=
204,204,204);border-left-style:solid;padding-left:1ex"> half the=C2=A0minin=
g equipment gets shut off.<br>
The amount of hashes/second is such that it is currently, lets just say, qu=
ite<br>
secure against any takeover.<br></blockquote><div><br></div><div>The equipm=
ent won&#39;t be simply turned off, it will be up for grabs.</div><div><br>=
</div><div>Please check this web sites:</div><div><br></div><div><a href=3D=
"https://nicehash.com/">https://nicehash.com/</a></div><div><a href=3D"http=
s://www.multipool.us/">https://www.multipool.us/</a>=C2=A0</div><div><br></=
div><div>One can use them in the same way he uses normal mining pools, and =
they switch between different chains.</div><div>Say, <a href=3D"http://mult=
ipool.us">multipool.us</a> can switch between BTC and PPC (Peercoin).</div>=
<div>Mining BTC will be less profitable after a halving, so a miner who is =
willing to maximize his profits might use multipool to auto-switch to somet=
hing more profitable.</div><div>Which might be attack-on-Bitcoin.</div><div=
>E.g. if 60% of bitcoin&#39;s total hashrate is available via &quot;multipo=
ols&quot;, one can try to pull of a double-spending attack.</div><div>=C2=
=A0<br></div><blockquote 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;padding-left:1ex">Your document makes a long series of assumpti=
ons about how this can turn out<br>
bad with each individually is implausible, together are just fiction.<br></=
blockquote><div><br></div><div>It sounds like you failed to grasp even basi=
cs.</div></div></div></div>

--047d7b4721e08d49e20506457057--