MIME-Version: 1.0
In-Reply-To: <CAKzdR-rPoByn=+CgsTc1ZnLkjwtYyJnbQLbn-VHOvz0dLciefQ@mail.gmail.com>
References: <CAKzdR-rPoByn=+CgsTc1ZnLkjwtYyJnbQLbn-VHOvz0dLciefQ@mail.gmail.com>
Date: Mon, 5 Oct 2015 18:56:38 +0200
Message-ID: <CA+w+GKSNa3TWgHXrp3=3gXdAbE6vVjW_uzus3_2YG9gzKJSskg@mail.gmail.com>
From: Mike Hearn <hearn@vinumeris.com>
To: Sergio Demian Lerner <sergio.d.lerner@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b4142c89a521f05215e65ca
Cc: bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] This thread is not about the soft/hard fork
 technical debate
Precedence: list

--047d7b4142c89a521f05215e65ca
Content-Type: text/plain; charset=UTF-8

Hey Sergio,

To clarify: my *single* objection is that CLTV should be a hard fork. I
haven't been raising never-ending technical objections, there's only one.

I *have* been answering all the various reasons being brought up why I'm
wrong and soft forks are awesome .... and there do seem to be a limitless
number of such emails .... but on my side it's still just a single
objection. If CLTV is a hard fork then I won't be objecting anymore, right?

CLTV deployment is clearly controversial. Many developers other than me
have noted that hard forks are cleaner, and have other desirable
properties. I'm not the only one who sees a big question mark over soft
forks.

As everyone in the Bitcoin community has been clearly told that
controversial changes to the consensus rules must not happen, it's clear
that CLTV cannot happen in its current form.

Now I'll be frank - you are quite correct that I fully expect the Core
maintainers to ignore this controversy and do CLTV as a soft fork anyway.
I'm a cynic. I don't think "everyone must agree" is workable and have said
so from the start. Faced with a choice of going back on their public
statements or having to make changes to something they clearly want, I
expect them to redefine what "real consensus" means. I hope I'm wrong, but
if I'm not ..... well, at least everyone will see what Gavin and I have
been talking about for so many months.

But I'd rather the opcode is tweaked. There's real financial risks to a
soft fork.

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

<div dir=3D"ltr">Hey Sergio,<div><br></div><div>To clarify: my <i>single</i=
>=C2=A0objection is that CLTV should be a hard fork. I haven&#39;t been rai=
sing never-ending technical objections, there&#39;s only one.</div><div><br=
></div><div>I <i>have</i> been answering all the various reasons being brou=
ght up why I&#39;m wrong and soft forks are awesome .... and there do seem =
to be a limitless number of such emails .... but on my side it&#39;s still =
just a single objection. If CLTV is a hard fork then I won&#39;t be objecti=
ng anymore, right?</div><div><br></div><div>CLTV deployment is clearly cont=
roversial. Many developers other than me have noted that hard forks are cle=
aner, and have other desirable properties. I&#39;m not the only one who see=
s a big question mark over soft forks.</div><div><br></div><div>As everyone=
 in the Bitcoin community has been clearly told that controversial changes =
to the consensus rules must not happen, it&#39;s clear that CLTV cannot hap=
pen in its current form.</div><div><br></div><div><div>Now I&#39;ll be fran=
k - you are quite correct that I fully expect the Core maintainers to ignor=
e this controversy and do CLTV as a soft fork anyway. I&#39;m a cynic. I do=
n&#39;t think &quot;everyone must agree&quot; is workable and have said so =
from the start. Faced with a choice of going back on their public statement=
s or having to make changes to something they clearly want, I expect them t=
o redefine what &quot;real consensus&quot; means. I hope I&#39;m wrong, but=
 if I&#39;m not ..... well, at least everyone will see what Gavin and I hav=
e been talking about for so many months.</div></div><div><br></div><div>But=
 I&#39;d rather the opcode is tweaked. There&#39;s real financial risks to =
a soft fork.</div></div>

--047d7b4142c89a521f05215e65ca--