MIME-Version: 1.0
In-Reply-To: <CAA33663-B688-4D53-8BED-85B4E67EFA0A@gmail.com>
References: <CAPg+sBgs-ouEMu=LOVCmOyCGwfM1Ygxooz0shyvAuHDGGZYfJw@mail.gmail.com>
	<CAPg+sBgugLSVEwDLXhgey86_rM2fTjGWXFuXsiZioJKCZiHiNg@mail.gmail.com>
	<CA+w+GKTfBNsQm0X27+QeMmLvJXuX0H=8+ij_GU6mkGnWn-poZA@mail.gmail.com>
	<CAA33663-B688-4D53-8BED-85B4E67EFA0A@gmail.com>
Date: Thu, 23 Jul 2015 00:01:32 +0200
Message-ID: <CA+w+GKQ_b0gMFov24nt8ZX89=GDWTpX9J15sj=fuicQBqBVcag@mail.gmail.com>
From: Mike Hearn <hearn@vinumeris.com>
To: Eric Lombrozo <elombrozo@gmail.com>
Content-Type: multipart/alternative; boundary=001a1141d818ea2b44051b7de9a6
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Bitcoin Core and hard forks
Precedence: list

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

>
> Until we=E2=80=99re able to merge blockchain forks like we=E2=80=99re abl=
e to merge git
> repo forks, the safest option is no fork.
>

Block chain forks merge in the same way as git forks all the time, that's
how the reorg algorithm works. Transactions that didn't make it into the
post-reorg chain go back into the mempool and miners attempt to reinclude
them: this is the "merge" process. If they now conflict with other
transactions they are dropped and this is "resolving merge conflicts".

However you have to want to merge with the new chain. If your software is
programmed not to do that out of some bizarre belief that throttling your
own user base is a good idea, then of course, no merge happens. Once you
stop telling your computer to do that, you can then merge (reorg) back onto
the main chain again.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div style=3D"word-wrap:break-word"><div><div>Un=
til we=E2=80=99re able to merge blockchain forks like we=E2=80=99re able to=
 merge git repo forks, the safest option is no fork.</div></div></div></blo=
ckquote><div><br></div><div>Block chain forks merge in the same way as git =
forks all the time, that&#39;s how the reorg algorithm works. Transactions =
that didn&#39;t make it into the post-reorg chain go back into the mempool =
and miners attempt to reinclude them: this is the &quot;merge&quot; process=
. If they now conflict with other transactions they are dropped and this is=
 &quot;resolving merge conflicts&quot;.</div><div><br></div><div>However yo=
u have to want to merge with the new chain. If your software is programmed =
not to do that out of some bizarre belief that throttling your own user bas=
e is a good idea, then of course, no merge happens. Once you stop telling y=
our computer to do that, you can then merge (reorg) back onto the main chai=
n again.</div><div><br></div></div></div></div>

--001a1141d818ea2b44051b7de9a6--