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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jeremie.dl@gmail.com>) id 1XjEBA-0003Z8-8W
for bitcoin-development@lists.sourceforge.net;
Tue, 28 Oct 2014 21:19:48 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.218.47 as permitted sender)
client-ip=209.85.218.47; envelope-from=jeremie.dl@gmail.com;
helo=mail-oi0-f47.google.com;
Received: from mail-oi0-f47.google.com ([209.85.218.47])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1XjEB9-0004ua-2T
for bitcoin-development@lists.sourceforge.net;
Tue, 28 Oct 2014 21:19:48 +0000
Received: by mail-oi0-f47.google.com with SMTP id a3so657737oib.34
for <bitcoin-development@lists.sourceforge.net>;
Tue, 28 Oct 2014 14:19:41 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.202.76.68 with SMTP id z65mr3706423oia.41.1414531181368;
Tue, 28 Oct 2014 14:19:41 -0700 (PDT)
Received: by 10.76.134.38 with HTTP; Tue, 28 Oct 2014 14:19:41 -0700 (PDT)
In-Reply-To: <CAE28kUSqqcsMJArK29nG+UCiTX9buiJbQoMb30-oH-G=eFxrnQ@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>
<CAJHLa0M20QjBOwhOwJWJUcPBLzmaX1uuPy-6ytvJQWLZy68aeg@mail.gmail.com>
<CAE28kUS7cr3i-pSew6Y+xvfLEY5D1mi4oHU-GXv+jEf-i_8sVQ@mail.gmail.com>
<CABsx9T1RPkif1+DEsOLrFfr-sE=FCs_B5C5aZzKr6HZCHw15ag@mail.gmail.com>
<CADfmNEk40DTHDB8if_y_2i_Omoszd_BgcSxf-oS+ZcQB0tZZhg@mail.gmail.com>
<CAAS2fgSiz-XRVQ4V+KbrTUWG4=g=WGf8c-pF4b4fFnfyU9HOqQ@mail.gmail.com>
<CAAS2fgRjwg_XyvzHbMhmaiW85LmmsW3YiXHyhpKMHd2a03pH2Q@mail.gmail.com>
<CAE28kUSqqcsMJArK29nG+UCiTX9buiJbQoMb30-oH-G=eFxrnQ@mail.gmail.com>
Date: Tue, 28 Oct 2014 22:19:41 +0100
Message-ID: <CAJqsvLCG2Cv=7wzDLotunEUTnAvdxVLSGrMEtkAnmdoBgONBsg@mail.gmail.com>
From: =?UTF-8?B?SsOpcsOpbWllIER1Ym9pcy1MYWNvc3Rl?= <jeremie.dl@gmail.com>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -0.4 (/)
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
(jeremie.dl[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.2 MISSING_HEADERS Missing To: header
-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: 1XjEB9-0004ua-2T
Subject: Re: [Bitcoin-development] Fwd: 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: Tue, 28 Oct 2014 21:19:48 -0000
Answering today's concerns with yesterday's facts is dangerous,
especially with bitcoin on a 4 years period. I personally consider all
arguments like "we went through once, and nothing special. So no
disturbance worthy of discussion to expect" baseless.
Also, starting a topic with mentions of "death" is not leading to any
useful discussion.
@Topic starters: don't oversell your topic with that kind of
vocabulary hype. "death by halving", seriously?
@Everybody else: don't focus on the chosen vocabulary, or use it to
discard what might be a relevant discussion topic.
The fact that a topic was brought up many times since a long time,
does not mean it is not relevant. It only means it is a recurring
concern. I read no convincing argument against a significant
disturbance of the mining market to come. The fact that it is known in
advance is no counter argument to me.
Environmental conditions will have changed so much, the next halving
occurence might have nothing to do with the previous one, and it
should be perfectly ok to discuss it instead of putting the whole
thing under the carpet.
What is most important to the discussion to me: the main difference
between the last halving and the one to come is the relative weight of
ideology vs. rationality in miners's motivations. Effectively putting
us closer to the original bitcoin premises (miners fully rational).
Miners were close to being 100% individuals last halving, they are now
largely for-profit companies. This isn't a change we can overlook with
pure maths or with previous experience.
Jeremie DL
2014-10-28 21:36 GMT+01:00 Gregory Maxwell <gmaxwell@gmail.com>:
> On Tue, Oct 28, 2014 at 8:17 PM, Ferdinando M. Ametrano
> <ferdinando.ametrano@gmail.com> wrote:
>>
>> On Oct 25, 2014 9:19 PM, "Gavin Andresen" <gavinandresen@gmail.com> wrote:
>> > We had a halving, and it was a non-event.
>> > Is there some reason to believe next time will be different?
>>
>> In november 2008 bitcoin was a much younger ecosystem,
>
> Or very old, indeed, if you are using unsigned arithmetic. [...]
>
>> and the halving happened during a quite stable positive price trend
>
> Hardly,
>
> http://bitcoincharts.com/charts/mtgoxUSD#rg60zczsg2012-10-01zeg2012-12-01ztgSzm1g10zm2g25zv
>
>> Moreover, halving is not strictly necessary to respect the spirit of Nakamoto's monetary rule
>
> It isn't, but many people have performed planning around the current
> behaviour. The current behaviour has also not shown itself to be
> problematic (and we've actually experienced its largest effect already
> without incident), and there are arguable benefits like encouraging
> investment in mining infrastructure.
>
> This thread is, in my opinion, a waste of time. It's yet again
> another perennial bikeshedding proposal brought up many times since at
> least 2011, suggesting random changes for
> non-existing(/not-yet-existing) issues.
>
> There is a lot more complexity to the system than the subsidy schedule.
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
2014-10-28 21:57 GMT+01:00 Alex Mizrahi <alex.mizrahi@gmail.com>:
>
>>
>> This thread is, in my opinion, a waste of time. It's yet again
>> another perennial bikeshedding proposal brought up many times since at
>> least 2011, suggesting random changes for
>> non-existing(/not-yet-existing) issues.
>>
>> There is a lot more complexity to the system than the subsidy schedule.
>
>
> Well, the main question is what makes Bitcoin secure.
> It is secured by proofs of work which are produced by miners.
> Miners have economic incentives to play by the rules; in simple terms, that
> is more profitable than performing attacks.
>
> So the question is, why and when it works? It would be nice to know the
> boundaries, no?
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
|
