public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Wladimir <laanwj@gmail.com>
To: Peter R <peter_r@gmx.com>
Cc: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Let's kill Bitcoin Core and allow the green shoots of a garden of new implementations to grow from its fertile ashes
Date: Tue, 1 Sep 2015 14:24:37 +0200	[thread overview]
Message-ID: <CA+s+GJCuFSUDvQ8bBRAtQT2mMPmLoRD9wXuiJZW3A4jKaVXVhQ@mail.gmail.com> (raw)
In-Reply-To: <CC252814-9AF6-4A28-926E-EE83C517E440@gmx.com>

On Tue, Sep 1, 2015 at 4:16 AM, Peter R via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> I agree, s7r, that Bitcoin Core represents the most stable code base.  To

What about the people that like stability, that appreciate bitcoin as
a "digital gold", and like all this 'excitement' like a hole in the
head?

Instead of creating hardforks and all the drama around it I'd
encourage to do your experiments on sidechains, or altcoins. Forks of
the bitcoin chain wil needlessly confuse matters, especially if they
all gain their share of users. In theory an hardfork would be no
different than an altcoin with shared history, but without proper
measures "crosstalk" between forks of the same chain can make for a
messy separation.
(A fact often ignored, because those proposing forks assume they can
just run over people on the other side of the fork by sake of their
popularity)

Also please don't confuse alternative implementations of the node
software - btcd, obelisk, etc - that try to implement the consensus
rules as faithfully as they can, or even use bitcoin core's consensus
code directly - with deliberate rule changes as done in bitcoin XT.
The former can cause an accidental fork (which will probably be
repaired), the latter exist to split off their chain.

Wladimir


  parent reply	other threads:[~2015-09-01 12:24 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31 20:06 [bitcoin-dev] Your Gmaxwell exchange Monarch
2015-08-31 20:27 ` Justus Ranvier
2015-08-31 20:48   ` Monarch
2015-08-31 21:24     ` Allen Piscitello
2015-08-31 21:42       ` Monarch
2015-08-31 21:54         ` Justus Ranvier
2015-08-31 22:53           ` Monarch
2015-08-31 23:24             ` Justus Ranvier
2015-09-01  0:02             ` Milly Bitcoin
2015-09-01  9:25           ` Jorge Timón
2015-08-31 23:32       ` Peter R
2015-08-31 23:47         ` s7r
2015-09-01  2:16           ` [bitcoin-dev] Let's kill Bitcoin Core and allow the green shoots of a garden of new implementations to grow from its fertile ashes Peter R
2015-09-01  2:25             ` Gregory Maxwell
2015-09-01  8:42             ` Adam Back
2015-09-01 10:16               ` Chris D'Costa
2015-09-01 11:20                 ` Monarch
2015-09-01 12:24             ` Wladimir [this message]
2015-09-01 22:06             ` s7r
2015-09-01 11:44           ` [bitcoin-dev] Your Gmaxwell exchange Monarch
2015-09-01 11:11         ` Monarch
2015-09-01 15:59           ` Dave Collins
2015-09-01 16:51             ` Monarch
2015-09-01 18:37               ` Eric Voskuil
2015-09-01 20:08                 ` Monarch

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=CA+s+GJCuFSUDvQ8bBRAtQT2mMPmLoRD9wXuiJZW3A4jKaVXVhQ@mail.gmail.com \
    --to=laanwj@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=peter_r@gmx.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