From: Tom Zander <tomz@freedommail.ch>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Bitcoin Classic 1.2.0 released
Date: Sun, 08 Jan 2017 00:08:29 +0100 [thread overview]
Message-ID: <10846872.WfBIm3d0e7@cherry> (raw)
In-Reply-To: <CADJgMzvsizuxPCRKcVKA+SHxK0Dp92Bnw1xag+oUFLrvU6Lw7A@mail.gmail.com>
On Saturday, 7 January 2017 21:15:11 CET Btc Drak via bitcoin-dev wrote:
> There actually isn't an activation threshold in Bitcoin Classic.
Thats partly correct.
There is just not a formal one, there very much is an informal and practical
threshold.
I, and I'm not alone in this, think that a formal vote or an algorithm to
decide something will happen or not reeks too much like central planning and
more importantly that it is too inflexible for real world use.
Its fine for simple upgrades, and we have seen lots of success there.
It would be a mistake to think that miners can just start mining with
Classic and make something that Core doesn't understand. That would have
negative effects and thus won't happen. Less social people will ask why and
maybe ask how we avoid this. They misunderstand the social and economic
parts of Bitcoin.
The block size is an ongoing debate.
I find it very hard to believe that all the people replying in outrage to my
release announcement completely missed this.
I see no point in bringing it up in a BIP or on this list as some central
cabal that can make decisions for or against. It is in actual fact being
decided in the real world, out of yours and my control.
Classic is a tool to that end. No more. No less.
--
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel
next prev parent reply other threads:[~2017-01-07 23:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 10:16 [bitcoin-dev] Bitcoin Classic 1.2.0 released Tom Zander
2017-01-07 8:13 ` 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 [this message]
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=10846872.WfBIm3d0e7@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