public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "NxtChg" <nxtchg@hush.com>
To: "Eric Lombrozo" <elombrozo@gmail.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Annoucing Not-BitcoinXT
Date: Tue, 18 Aug 2015 12:46:11 +0300	[thread overview]
Message-ID: <20150818094612.2344943128@smtp.hushmail.com> (raw)
In-Reply-To: <CE3B7411-2863-4D6B-85B0-4F28D4D7F391@gmail.com>

Eric,

>FWIW...

These are all good points and I agree with most of them. Yes, the block size debate is a lucky historical accident, which makes it easier for XT to pull off the split, but that's not the point.

The point is, the split _must_ happen because the centralized governance of Bitcoin became a bigger problem than the risks of a fork or larger blocks.

You cannot govern a decentralized currency with a centralized entity.

That's why we shouldn't fear hard forks - they are the new reality, and if we cannot set up a reliable process for them to happen then there _is_ no decentralized Bitcoin and we all might as well just give up and go home.

----

And that's why it would be nice to have a more complex voting mechanism in the block header (see this proposal for the new header format, for example: https://bitcointalk.org/index.php?topic=1151698) and other initiatives to make forking more reliable and user choice easier.

This is a better path than trying to suppress all forks by dictatorship methods of the few currently in power.



  parent reply	other threads:[~2015-08-18  9:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-16 22:34 [bitcoin-dev] Annoucing Not-BitcoinXT jyellen
2015-08-17  3:10 ` jl2012
2015-08-17  7:04 ` Peter Todd
2015-08-17 10:09 ` NxtChg
2015-08-17 12:40   ` Vali Zero
2015-08-17 13:34     ` NxtChg
2015-08-17 14:03       ` Eric Lombrozo
2015-08-17 14:09         ` Levin Keller
2015-08-17 14:30           ` Eric Lombrozo
2015-08-17 14:36         ` Adam Back
2015-08-17 14:58           ` GC
2015-08-17 15:03           ` Levin Keller
2015-08-17 15:07             ` Eric Lombrozo
2015-08-19  3:49           ` odinn
2015-08-17 15:10         ` NxtChg
2015-08-17 16:37       ` Eric Lombrozo
2015-08-17 16:55         ` Eric Lombrozo
2015-08-18  4:37           ` Dave Scotese
2015-08-18  5:13             ` GC
2015-08-18  5:33               ` Dave Scotese
2015-08-18  9:46         ` NxtChg [this message]
2015-08-19  9:47           ` Jorge Timón

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=20150818094612.2344943128@smtp.hushmail.com \
    --to=nxtchg@hush.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=elombrozo@gmail.com \
    /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