From: Tom Zander <tomz@freedommail.ch>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] Bitcoin Classic 1.2.0 released
Date: Fri, 06 Jan 2017 11:16:28 +0100 [thread overview]
Message-ID: <7169224.bI6Cz5OEL8@cherry> (raw)
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
next reply other threads:[~2017-01-06 10:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 10:16 Tom Zander [this message]
2017-01-07 8:13 ` [bitcoin-dev] Bitcoin Classic 1.2.0 released Jonas Schnelli
2017-01-07 8:55 ` Eric Lombrozo
2017-01-07 15:15 ` Tom Zander
2017-01-07 20:12 ` Chris Priest
2017-01-07 20:17 ` David Vorick
2017-01-07 20:26 ` Chris Priest
2017-01-07 21:14 ` Eric Voskuil
2017-01-07 23:10 ` Aymeric Vitte
2017-01-07 23:49 ` Eric Voskuil
2017-01-08 0:28 ` Eric Lombrozo
2017-01-08 1:58 ` Chris Priest
2017-01-07 21:15 ` Btc Drak
2017-01-07 23:08 ` Tom Zander
2017-01-08 0:32 ` Eric Voskuil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7169224.bI6Cz5OEL8@cherry \
--to=tomz@freedommail.ch \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox