Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.217.181 as permitted sender)
	client-ip=209.85.217.181; envelope-from=elombrozo@gmail.com;
	helo=mail-lb0-f181.google.com; 
MIME-Version: 1.0
In-Reply-To: <CADJgMztZuqt1BM8S2W1nOOBET=na+L+SZe4RRPdLU4tnbA-7cA@mail.gmail.com>
References: <3698747.VeHb3lFFLZ@crushinator>
	<CADJgMztZuqt1BM8S2W1nOOBET=na+L+SZe4RRPdLU4tnbA-7cA@mail.gmail.com>
Date: Sun, 31 May 2015 03:01:53 -0700
Message-ID: <CABr1YTcSPcJBb-ZFQ59cYuywix4bfKpic_KjBProiAZ47o8fPg@mail.gmail.com>
From: Eric Lombrozo <elombrozo@gmail.com>
To: Btc Drak <btcdrak@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c3728e8228fc05175dcc16
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Proposal: A measured response to save
 Bitcoin Core
Precedence: list

--001a11c3728e8228fc05175dcc16
Content-Type: text/plain; charset=UTF-8

Drak,

I mostly agree with your assessment...except for your last claim.

Not that I wouldn't like to find a way to avoid politics, but like I've
argued before, it is inevitable that sooner or later any consensus protocol
that seeks dynamism will encounter politics.

The block size discussion, while ultimately necessary, for now is in the
best case merely serving as an example of the kind of political issues we
*really* need to be finding some solution for...and in the worst case is a
distraction and evasion.

Some protocol updates will be merely technical optimizations or feature
enhancements that are fairly uncontroversial...but some will inevitably be
highly controversial with real-world economic consequences, winners and
losers. We lack a process for deciding these issues. No matter how
sophistocated we make the protocol, somethings will inevitably require
external input to make these issues decidable...it is a Goedelian
implication. This external input could be some sort of vote (of which
hashing power is a particular kind) or perhaps something else.

There's something to be said for building the dynamics of hard forks *into*
our model rather than avoiding it at all costs.  However, forks are the
easy part. The difficulty is in merging different branches. Perhaps we
should learn a thing or two from git. Perhaps the question we should be
asking is not "how do we avoid hard forks" but "how can we design the
network to allow for merging?"

- Eric Lombrozo

--001a11c3728e8228fc05175dcc16
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">Drak,</p>
<p dir=3D"ltr">I mostly agree with your assessment...except for your last c=
laim.</p>
<p dir=3D"ltr">Not that I wouldn&#39;t like to find a way to avoid politics=
, but like I&#39;ve argued before, it is inevitable that sooner or later an=
y consensus protocol that seeks dynamism will encounter politics.</p>
<p dir=3D"ltr">The block size discussion, while ultimately necessary, for n=
ow is in the best case merely serving as an example of the kind of politica=
l issues we *really* need to be finding some solution for...and in the wors=
t case is a distraction and evasion.</p>
<p dir=3D"ltr">Some protocol updates will be merely technical optimizations=
 or feature enhancements that are fairly uncontroversial...but some will in=
evitably be highly controversial with real-world economic consequences, win=
ners and losers. We lack a process for deciding these issues. No matter how=
 sophistocated we make the protocol, somethings will inevitably require ext=
ernal input to make these issues decidable...it is a Goedelian implication.=
 This external input could be some sort of vote (of which hashing power is =
a particular kind) or perhaps something else.</p>
<p dir=3D"ltr">There&#39;s something to be said for building the dynamics o=
f hard forks *into* our model rather than avoiding it at all costs.=C2=A0 H=
owever, forks are the easy part. The difficulty is in merging different bra=
nches. Perhaps we should learn a thing or two from git. Perhaps the questio=
n we should be asking is not &quot;how do we avoid hard forks&quot; but &qu=
ot;how can we design the network to allow for merging?&quot;</p>
<p dir=3D"ltr">- Eric Lombrozo</p>

--001a11c3728e8228fc05175dcc16--