Bitcoin Classic only activates if 75% of the network adopts it. That is not irresponsible or dangerous. It would only be dangerous if it activates at 50%, because that would create a situation where its not clear which side of the fork has the most proof of work.
On 1/7/17, Eric Lombrozo via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote: > 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 >> > _______________________________________________ bitcoin-dev mailing list bitcoin-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev