From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id CDFDB87A for ; 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 ; Sat, 7 Jan 2017 08:55:21 +0000 (UTC) Received: by mail-yw0-f193.google.com with SMTP id 17so6261031ywk.2 for ; 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 Date: Sat, 7 Jan 2017 00:55:19 -0800 Message-ID: To: Tom Zander , Bitcoin Protocol Discussion 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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; > > > > 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

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.


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=A0htt= ps://github.com/bitcoinclassic/bitcoinclassic/tree/v1.2.0/doc=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.


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;

=C2=A0<https://bitcoinclassic.com/gettingstart= ed.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 th= e
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.<= br> Classic presents top notch quality processes in this release, to help anyon= e
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<= br> 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/bitcoinc= lassic/bitcoinclassic/releases/tag/v1.2.0

--
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel<= /a>
_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.= linuxfoundation.org
https://lists.linuxfoundation.org= /mailman/listinfo/bitcoin-dev

--001a114fab1051a22805457d4bb9--