MIME-Version: 1.0
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
Subject: Re: [bitcoin-dev] Bitcoin Classic 1.2.0 released
Precedence: list

--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&#39;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">&lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundati=
on.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</a>&gt;</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&lt;<a href=3D"https://bitcoinclassic.com/gettingstarted.html" rel=3D=
"noreferrer" target=3D"_blank">https://bitcoinclassic.com/<wbr>gettingstart=
ed.html</a>&gt;<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--