From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id B8B46307 for ; Thu, 23 Jul 2015 01:53:39 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-pa0-f50.google.com (mail-pa0-f50.google.com [209.85.220.50]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 55206F7 for ; Thu, 23 Jul 2015 01:53:39 +0000 (UTC) Received: by pacan13 with SMTP id an13so149467919pac.1 for ; Wed, 22 Jul 2015 18:53:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to; bh=5fE61RyvR60vgenol+wCqthHZhhPYbnTB0mT0Qzv3SU=; b=oQUk3qA6rftU4xpfY120QT/EMvX5P38NiHD4bP0u+x+Ik2kfMAFvKolHJLjx8/opRF UfPHVJYComjBsMBh3LgmR2k+iTKxiI8s3Vp+eHm0lbhLpH+FiDWgZ1OIDFg5qEJ95VGq FsgraFJvYTiBjilXYGZ/vUeicp+rqLlxIJ45sDxYxzpgEDwmwJDG5i7kfcuoTYgbpdiN YBelg/vC1mhHZzOSU1qsyIIlVlbPmrgIAcN42noj/S0JcU6Tb38S/YDvEhna0fcIr5wj EYyyqf5m2hFsFqZoYonscZGzd6bT3wPOl/vXrY5AdDclQ/UqNDbCev2vIIQkuvRzpxrX VMcg== X-Received: by 10.70.37.207 with SMTP id a15mr12707986pdk.4.1437616418957; Wed, 22 Jul 2015 18:53:38 -0700 (PDT) Received: from [192.168.1.107] (cpe-76-167-237-202.san.res.rr.com. [76.167.237.202]) by smtp.gmail.com with ESMTPSA id p1sm5595854pdb.3.2015.07.22.18.53.37 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 22 Jul 2015 18:53:37 -0700 (PDT) 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 X-Pgp-Agent: GPGMail 2.5b6 From: Eric Lombrozo In-Reply-To: Date: Wed, 22 Jul 2015 18:53:36 -0700 Message-Id: <2795DFE0-C544-432D-BE01-6DEF7DC4FAB1@gmail.com> References: To: Mike Hearn X-Mailer: Apple Mail (2.2098) X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: bitcoin-dev@lists.linuxfoundation.org Subject: Re: [bitcoin-dev] Bitcoin Core and hard forks X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jul 2015 01:53:39 -0000 --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 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
On = Jul 22, 2015, at 3:01 PM, Mike Hearn <hearn@vinumeris.com>= wrote:

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.

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.


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-- --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--