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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1Xi68U-00027z-Bi
for bitcoin-development@lists.sourceforge.net;
Sat, 25 Oct 2014 18:32:22 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bitpay.com
designates 209.85.213.171 as permitted sender)
client-ip=209.85.213.171; envelope-from=jgarzik@bitpay.com;
helo=mail-ig0-f171.google.com;
Received: from mail-ig0-f171.google.com ([209.85.213.171])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Xi68T-0004cq-D3
for bitcoin-development@lists.sourceforge.net;
Sat, 25 Oct 2014 18:32:22 +0000
Received: by mail-ig0-f171.google.com with SMTP id l13so2803209iga.4
for <bitcoin-development@lists.sourceforge.net>;
Sat, 25 Oct 2014 11:32:16 -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=iI0LkIKgQw8kPb3jRGc45psZOB4dtM+ThaqhYcBkG3U=;
b=IG3AVrjVxaEe5AEf65/+0y6L6TQ3YlbDkI1FPgzq2uydBq1XC5wgi7NGNQz14ZdtJH
30RM1agE+MXwGsl1akOmXHjcSOs9l3BUucB1raiulAr+b8p2/YuYz+FWbwW3NC6/MWyr
TX/cTsYf37M84iqfVY9FxOSB2TZ3j4hKsGpL8JLbJ+NclWC+RR+h8MFiZjCS1MTbrhns
VtBnaOCZ6e1MpOLhetSDjVuUdYDbycXOL7a3qxuHt5vw2xu1lN27prVsHuCE+25MrKdP
tUNDO27a3Y47pqAHdoFLocoN+71bE+jI10wxYgPPtJ9M4mEyhpDoQsRfyWjrzOCqaTdl
a9rA==
X-Gm-Message-State: ALoCoQlrjwOHwj2WU+/3T1eWDMF7iExNlLLciyr2ObZ4MyJFqusExuPGHhunW2I48ECnt24QhngM
X-Received: by 10.50.3.4 with SMTP id 4mr11656534igy.22.1414261935987; Sat, 25
Oct 2014 11:32:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.156.193 with HTTP; Sat, 25 Oct 2014 11:31:55 -0700 (PDT)
In-Reply-To: <CAE28kUSPb3ZC1nJyX7H__7cAgXvOvPbZ+Tub+htGd5+tujZndg@mail.gmail.com>
References: <CAE28kUS-uDbd_Br3H5BxwRm1PZFpOwLhcyyZT9b1_VfRaBC9jw@mail.gmail.com>
<CAJHLa0PeB-DMs2zo680FRvaejV-K97k2g0Ti9pPdaNeH+gYmog@mail.gmail.com>
<CAE28kUSPb3ZC1nJyX7H__7cAgXvOvPbZ+Tub+htGd5+tujZndg@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Sat, 25 Oct 2014 14:31:55 -0400
Message-ID: <CAJHLa0M20QjBOwhOwJWJUcPBLzmaX1uuPy-6ytvJQWLZy68aeg@mail.gmail.com>
To: Alex Mizrahi <alex.mizrahi@gmail.com>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.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 SPF_PASS SPF: sender matches SPF record
-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: 1Xi68T-0004cq-D3
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
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 18:32:22 -0000
It is an overly-simplistic miner model to assume altruism is
necessary. The hashpower market is maturing in the direction of
financial instruments, where the owner of the hashpower is not
necessarily the one receiving income. These are becoming tradeable
instruments, and derivatives and hedging are built on top of that.
Risk is hedged at each layer. Market players also forge agreements
with miners, and receive -negative- value if hashpower is simply shut
down.
Simplistic models cannot predict what hashpower does in the face of
business-to-business medium- and long-term contracts.
On Sat, Oct 25, 2014 at 2:22 PM, Alex Mizrahi <alex.mizrahi@gmail.com> wrote:
>
>>
>> "Flag day" herd behavior like this is unlikely for well informed and
>> well prepared market participants.
>
>
> It is simply rational to turn your mining device off until difficulty
> adjusts.
> Keeping mining for 2+ weeks when it costs you money is an altruistic
> behavior, we shouldn't rely on this.
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> 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/
|
