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
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
|
Return-Path: <elombrozo@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id CDFDB87A
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 7 Jan 2017 08:55:21 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-yw0-f193.google.com (mail-yw0-f193.google.com
[209.85.161.193])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 2F6D0A1
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 7 Jan 2017 08:55:21 +0000 (UTC)
Received: by mail-yw0-f193.google.com with SMTP id 17so6261031ywk.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 07 Jan 2017 00:55:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to;
bh=3uJwaxdjTLjVf81l0t4iMCLSAlz9elZv4GsHCmqG5jI=;
b=prTaQKp6UPGAuO5B9V1g3R3pCUW7eE/v8Wac26yD2XVlAiBcxtHsks0EgARWusnNHH
0pntTQtscZ9VbDw7uCF+qldtlW2gRVMZGtQpvvD/bPCCNcFmbHc8o3G7gC7M8W8VUgaa
gXtOMQdjABjha5EBSNVANyHmb9e7CkAi/ZnwVYJVUBt/gfSQaP33TrPbHKZBO25eE/S2
ihO35hOWgHfUiZh4wyaHJvTNdq9Olh6t2veq01pYsSLGmo1sUrDEwCR312PK50YCmitC
a+firWu5Hd192OTJfp4Sh8FpzskaAWWrNf0FbnL4/rQSv5tqdd83veBvwDzf6t9HgbIQ
0CQg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to;
bh=3uJwaxdjTLjVf81l0t4iMCLSAlz9elZv4GsHCmqG5jI=;
b=d+9NLigX8e0Buq1cJbP6W0quHOs4Un/TQGM+2c8SVVfcz0boIwH01nP9J4D8eE+090
83Qk8R17QRK6pQtUqbG753eTXx3D2SqpKgsVG+XQd1oYWZ6PFrFW8V31yV7YghhPzk2H
7E9q3w2Xm6vjrkJVwn6i8c6a/U3GFR//Q/PJwDhsw5tYIE87Y33cB4dQH4UwdYODlNlJ
4+Jxyv9emgvaSRpsIrkJQH5Kdji5kT9g2tnFBkJlKSGOSOCZz0JEqwcAUMWrrleTYIHH
6C0nK2m1sFc0yBRoguf+sYuvqC1uX32K97KlS6HoMotrQx8A8VCvcoMuoR7JtD9PjsqZ
iF3A==
X-Gm-Message-State: AIkVDXL7kkMiQFvbl9RfMkCqi9we2IrBBKXT9eCos22cplbHBQMGoCtI3sgkAaxsbkjh94Iwuj9lLNBGBHKSPQ==
X-Received: by 10.13.212.149 with SMTP id w143mr2043332ywd.180.1483779320420;
Sat, 07 Jan 2017 00:55:20 -0800 (PST)
MIME-Version: 1.0
Received: by 10.37.109.138 with HTTP; Sat, 7 Jan 2017 00:55:19 -0800 (PST)
In-Reply-To: <7169224.bI6Cz5OEL8@cherry>
References: <7169224.bI6Cz5OEL8@cherry>
From: Eric Lombrozo <elombrozo@gmail.com>
Date: Sat, 7 Jan 2017 00:55:19 -0800
Message-ID: <CABr1YTfc0BZ21-mwMohqo8_v8D1QnYiGB_SMeCLwFChY2MV_zA@mail.gmail.com>
To: Tom Zander <tomz@freedommail.ch>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a114fab1051a22805457d4bb9
X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
RCVD_IN_DNSWL_NONE,
RCVD_IN_SORBS_SPAM autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] Bitcoin Classic 1.2.0 released
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol 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: Sat, 07 Jan 2017 08:55:21 -0000
--001a114fab1051a22805457d4bb9
Content-Type: text/plain; charset=UTF-8
Your release announcement does not make it clear that Bitcoin Classic is
incompatible with the current Bitcoin network and its consensus rules. It
is a hard fork on mainnet with no safe activation as well as including
other unsafe changes. There is also no BIP for the hard fork. There is also
no evidence of community wide consensus for such a hard fork. This is
dangerous and irresponsible.
It's wrong to announce software without correctly informing people about
the contents or risks. Furthermore, there are no release notes in
https://github.com/bitcoinclassic/bitcoinclassic/tree/v1.2.0/doc nor
changelog. Without those, it is almost impossible for average users to know
what is under the hood or what has changed and time consuming for
developers to assess.
On Fri, Jan 6, 2017 at 2:16 AM, Tom Zander via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Bitcoin Classic version 1.2.0 is now available from;
>
> <https://bitcoinclassic.com/gettingstarted.html>
>
> This is a new major version release, including new features, various
> bugfixes and performance improvements.
>
> This release marks a change in strategy for Bitcoin Classic, moving from
> the
> very conservative block size proposal based on compromise to one where
> Classic truly innovates and provides a long term solution for the market to
> choose and leave behind the restrictions of the old.
>
> The most visible change in this version is the decentralised block size
> solution where node operators decide on the maximum size.
>
> Bitcoin Classic is focused on providing users a way to get onto the Bitcoin
> network using a high quality validating node for a large set of use cases.
> Classic presents top notch quality processes in this release, to help
> anyone
> running Bitcoin.
>
> We include in this release various projects with the beta label. People who
> want to use the Classic node as an on-ramp to Bitcoin will find them
> interesting. These projects will need to be enabled in the config by those
> that want to test them.
>
> More background information on this release and Classic can be seen in this
> video: https://vimeo.com/192789752
> The full release notes are on github at
> https://github.com/bitcoinclassic/bitcoinclassic/releases/tag/v1.2.0
>
> --
> Tom Zander
> Blog: https://zander.github.io
> Vlog: https://vimeo.com/channels/tomscryptochannel
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--001a114fab1051a22805457d4bb9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">
<p class=3D"gmail-p1"><span class=3D"gmail-s1">Your release announcement do=
es not make it clear that Bitcoin Classic is incompatible with the current =
Bitcoin network and its consensus rules. It is a hard fork on mainnet with =
no safe activation as well as including other unsafe changes. There is also=
no BIP for the hard fork. There is also no evidence of community wide cons=
ensus for such a hard fork. This is dangerous and irresponsible.</span></p>
<p class=3D"gmail-p2"><span class=3D"gmail-s1"></span><br></p>
<p class=3D"gmail-p1"><span class=3D"gmail-s1">It's wrong to announce s=
oftware without correctly informing people about the contents or risks. Fur=
thermore, there are no release notes in=C2=A0<a href=3D"https://github.com/=
bitcoinclassic/bitcoinclassic/tree/v1.2.0/doc"><span class=3D"gmail-s2">htt=
ps://github.com/bitcoinclassic/bitcoinclassic/tree/v1.2.0/doc</span></a>=C2=
=A0nor changelog. Without those, it is almost impossible for average users =
to know what is under the hood or what has changed and time consuming for d=
evelopers to assess.</span></p></div><div class=3D"gmail_extra"><br><div cl=
ass=3D"gmail_quote">On Fri, Jan 6, 2017 at 2:16 AM, Tom Zander via bitcoin-=
dev <span dir=3D"ltr"><<a href=3D"mailto:bitcoin-dev@lists.linuxfoundati=
on.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</a>></sp=
an> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">Bitcoin Classic version 1.2.0 =
is now available from;<br>
<br>
=C2=A0<<a href=3D"https://bitcoinclassic.com/gettingstarted.html" rel=3D=
"noreferrer" target=3D"_blank">https://bitcoinclassic.com/<wbr>gettingstart=
ed.html</a>><br>
<br>
This is a new major version release, including new features, various<br>
bugfixes and performance improvements.<br>
<br>
This release marks a change in strategy for Bitcoin Classic, moving from th=
e<br>
very conservative block size proposal based on compromise to one where<br>
Classic truly innovates and provides a long term solution for the market to=
<br>
choose and leave behind the restrictions of the old.<br>
<br>
The most visible change in this version is the decentralised block size<br>
solution where node operators decide on the maximum size.<br>
<br>
Bitcoin Classic is focused on providing users a way to get onto the Bitcoin=
<br>
network using a high quality validating node for a large set of use cases.<=
br>
Classic presents top notch quality processes in this release, to help anyon=
e<br>
running Bitcoin.<br>
<br>
We include in this release various projects with the beta label. People who=
<br>
want to use the Classic node as an on-ramp to Bitcoin will find them<br>
interesting. These projects will need to be enabled in the config by those<=
br>
that want to test them.<br>
<br>
More background information on this release and Classic can be seen in this=
<br>
video: <a href=3D"https://vimeo.com/192789752" rel=3D"noreferrer" target=3D=
"_blank">https://vimeo.com/192789752</a><br>
The full release notes are on github at<br>
<a href=3D"https://github.com/bitcoinclassic/bitcoinclassic/releases/tag/v1=
.2.0" rel=3D"noreferrer" target=3D"_blank">https://github.com/<wbr>bitcoinc=
lassic/bitcoinclassic/<wbr>releases/tag/v1.2.0</a><br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
Tom Zander<br>
Blog: <a href=3D"https://zander.github.io" rel=3D"noreferrer" target=3D"_bl=
ank">https://zander.github.io</a><br>
Vlog: <a href=3D"https://vimeo.com/channels/tomscryptochannel" rel=3D"noref=
errer" target=3D"_blank">https://vimeo.com/channels/<wbr>tomscryptochannel<=
/a><br>
______________________________<wbr>_________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
<wbr>linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.<wbr>org=
/mailman/listinfo/bitcoin-<wbr>dev</a><br>
</font></span></blockquote></div><br></div>
--001a114fab1051a22805457d4bb9--
|
