MIME-Version: 1.0
In-Reply-To: <E3D72CF4-3D1C-4235-87F9-A035AFF28C27@gmail.com>
References: <CALqxMTFkgGx0FxMiZ77inOZSs_+TQ88Wpj-q-c12COkO9tP4gQ@mail.gmail.com>
	<CADJgMzv+cKPY9wrAzbk5pgQJS0=R9KWu-+EuppM=nmXs8RHxYg@mail.gmail.com>
	<20150819182010.GB12306@muck>
	<CADJgMzskK9iNoRzVr0BtK+XH-x2w5mGZtBiieQpwcGevnHRjGg@mail.gmail.com>
	<55D4D9C3.5070004@riseup.net>
	<C47D37EE-AE42-4175-AD6B-F6FD0841287B@gmail.com>
	<CABm2gDpAOQim63Q7r9r-Pv-K+FqizgDHNUmQ7uheGMuMt-e2QA@mail.gmail.com>
	<E3D72CF4-3D1C-4235-87F9-A035AFF28C27@gmail.com>
Date: Thu, 20 Aug 2015 00:00:09 +0200
Message-ID: <CABm2gDrefdHeYWF2y_o7A9NxRssC=ddHqY--ExxLv00TS4ShKQ@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
To: Eric Lombrozo <elombrozo@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin XT Fork
Precedence: list

On Wed, Aug 19, 2015 at 10:04 PM, Eric Lombrozo <elombrozo@gmail.com> wrote=
:
> But the consensus code should NOT be subject to the same commit policies=
=E2=80=A6and we should make an effort to separate the two clearly. And we s=
hould find a way to communicate the difference succinctly and clearly to la=
ypeople (which is something I think the XT opponents have been horrible at =
doing so far).

I think that effort is in progress (again, much slower that I would
like it to be) and it's called libconsensus.
Once we have libconsensus Bitcoin Core it's just another
implementation (even if it is the reference one) and it's not "the
specification of the consensus rules" which is a "privileged" position
that brings all sorts of misunderstandings and problems (the block
size debate is just one example).