Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Content-Type: multipart/signed;
	boundary="Apple-Mail=_C6B4FA20-98E1-4AD2-BFFB-6B752541E7EF";
	protocol="application/pgp-signature"; micalg=pgp-sha512
From: Eric Lombrozo <elombrozo@gmail.com>
In-Reply-To: <CA+w+GKQ_b0gMFov24nt8ZX89=GDWTpX9J15sj=fuicQBqBVcag@mail.gmail.com>
Date: Wed, 22 Jul 2015 18:53:36 -0700
Message-Id: <2795DFE0-C544-432D-BE01-6DEF7DC4FAB1@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>
	<CA+w+GKQ_b0gMFov24nt8ZX89=GDWTpX9J15sj=fuicQBqBVcag@mail.gmail.com>
To: Mike Hearn <hearn@vinumeris.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Bitcoin Core and hard forks
Precedence: list


--Apple-Mail=_C6B4FA20-98E1-4AD2-BFFB-6B752541E7EF
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_6FB3D1E3-BF8D-4B59-9F7A-B2D64CF95A7C"


--Apple-Mail=_6FB3D1E3-BF8D-4B59-9F7A-B2D64CF95A7C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

> On Jul 22, 2015, at 3:01 PM, Mike Hearn <hearn@vinumeris.com> wrote:
>=20
> Until 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.
>=20
> 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".
>=20
> 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.
>=20

Mike, you might be surprized to learn that there are other hard fork =
proposals out there besides increasing block size.


--Apple-Mail=_6FB3D1E3-BF8D-4B59-9F7A-B2D64CF95A7C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">On =
Jul 22, 2015, at 3:01 PM, Mike Hearn &lt;<a =
href=3D"mailto:hearn@vinumeris.com" class=3D"">hearn@vinumeris.com</a>&gt;=
 wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
dir=3D"ltr" class=3D""><div class=3D"gmail_extra"><div =
class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div =
style=3D"word-wrap:break-word" class=3D""><div class=3D""><div =
class=3D"">Until 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></blockquote><div class=3D""><br =
class=3D""></div><div class=3D"">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".</div><div class=3D""><br =
class=3D""></div><div class=3D"">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.</div><div class=3D""><br class=3D""></div></div></div></div>
</div></blockquote></div><br class=3D""><div class=3D"">Mike, you might =
be surprized to learn that there are other hard fork proposals out there =
besides increasing block size.<br class=3D""><div><blockquote =
type=3D"cite" class=3D""></blockquote></div></div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_6FB3D1E3-BF8D-4B59-9F7A-B2D64CF95A7C--

--Apple-Mail=_C6B4FA20-98E1-4AD2-BFFB-6B752541E7EF
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJVsEkgAAoJEJNAI64YFENUABwP/1Hkc/WO277S4d9wSDraIZZp
I/SzISaS8AaxIQ8ZPKpaU17I2GPNd54GhwMkpzRfgicfmNQp4JPWPCaxxUAvTJZq
ahfy/nnkCOSBoB66cd9M1wY08VKWHpz2/PKRKN51LJKzTdphha/KD1us5S28Zh5G
G7CE68h4k8h2DH/lDN3bd8rs1W4GNYMPdmP6VDJwDTZdQYDzH4K0exYV5mG87eVw
v+6ljVa1va3boITFQkm+k04ajwbaIQX1veLavlA0oQUta4Cw8VMnmPndir47oR8j
+KpqDBbtGwkf14E2vz/7cBpe2mdrYzikeVj4prSGuXpe7PCiJxw0tripytpt8XJr
U8keVsvxypF+pxiOX7ppvnw0oO+1fYzJP2dw3++JgQ8x9MPfQvXfts1unCjKIerM
nix10jMKJtpvI/bCgiHDmB42jL4RZQr3edmlBdkes0wyLCkrb5GbSUj48Zy+8500
fdQXmlKeujqw42Gx0Gg50dtGSv6l54tCeTaazeeF13cgNW+EzrBO3y66p3fn4JMj
sWCbnNMaIt8sBESmB6rf1pE9TyKsb7nT+njCdGSY+pLMiXDLY6f7FSuC6BTPMY3P
hS3hrStaWozTFzeEJXkQTbrsilvwBUVtHtk4qXrA62F7IB2tBqT16kcl7gazamkO
XEus2qjpGjPvh4FNmjES
=bMnt
-----END PGP SIGNATURE-----

--Apple-Mail=_C6B4FA20-98E1-4AD2-BFFB-6B752541E7EF--