From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <elombrozo@gmail.com> Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 4FD3D516 for <bitcoin-dev@lists.linuxfoundation.org>; Wed, 22 Jul 2015 21:56:55 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-pa0-f49.google.com (mail-pa0-f49.google.com [209.85.220.49]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id C534BE8 for <bitcoin-dev@lists.linuxfoundation.org>; Wed, 22 Jul 2015 21:56:54 +0000 (UTC) Received: by pabkd10 with SMTP id kd10so73038993pab.2 for <bitcoin-dev@lists.linuxfoundation.org>; Wed, 22 Jul 2015 14:56:54 -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=Hgu+I0voEpBlBPFUIZLBtd7Nj3gyPtVM3hWR5v/Bowg=; b=qrA5orduv5SgO/fV31E9V8MNheI8rKmKir8iDaHSfyn/Oh+7TWJ+o//2o/lLWts0+0 cn0rjcQdmUqX6K8Qi/Z4sLlSJsXOktORB5NhXvDRexQpnDLoBjQSUBxSNxnHgOZSjF3s 8msLhVl/2W1668UqF0+uG+pgP68IpYEhl2nu1h+rP13ZkbETa3+XhDjK7KNYQ6suw1Lc M06n8LS+Uz4iMvpE4/+nrwxA+8k1glDeZYLiFC3omTC2Ukc6ooeD/ttwfv19sPzKWrua +zEOOTQ0EVryJajIun5Lj0kCwnpa7wwT5k8y7pU6W4zVHQXiHN7WpjyK2eFtwkEEoVFF YaLA== X-Received: by 10.70.128.14 with SMTP id nk14mr7553790pdb.79.1437602214429; Wed, 22 Jul 2015 14:56:54 -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 tm3sm5088382pac.44.2015.07.22.14.56.52 (version=TLS1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 22 Jul 2015 14:56:53 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) Content-Type: multipart/signed; boundary="Apple-Mail=_EBB0F521-9695-42FE-B827-549CD54A7319"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Pgp-Agent: GPGMail 2.5b6 From: Eric Lombrozo <elombrozo@gmail.com> In-Reply-To: <CA+w+GKTfBNsQm0X27+QeMmLvJXuX0H=8+ij_GU6mkGnWn-poZA@mail.gmail.com> Date: Wed, 22 Jul 2015 14:56:50 -0700 Message-Id: <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> To: Mike Hearn <hearn@vinumeris.com> 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 <bitcoin-dev.lists.linuxfoundation.org> List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe> List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/> List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org> List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help> List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe> X-List-Received-Date: Wed, 22 Jul 2015 21:56:55 -0000 --Apple-Mail=_EBB0F521-9695-42FE-B827-549CD54A7319 Content-Type: multipart/alternative; boundary="Apple-Mail=_35703E66-5314-4F38-9821-A1F71F7ECCBF" --Apple-Mail=_35703E66-5314-4F38-9821-A1F71F7ECCBF Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Jul 22, 2015, at 2:43 PM, Mike Hearn via bitcoin-dev = <bitcoin-dev@lists.linuxfoundation.org> wrote: >=20 > Hi Pieter, >=20 > I think a core area of disagreement is this: > Bitcoin Core is not running the Bitcoin economy, and its developers = have no authority to set its rules. >=20 > In fact Bitcoin Core is running the Bitcoin economy, and its = developers do have the authority to set its rules. This is enforced by = the reality of ~100% market share and limited github commit access. >=20 > You may not like this situation, but it is what it is. By refusing to = make a release with different rules, people who disagree are faced with = only two options: >=20 > 1. Swallow it even if they hate it > 2. Fork the project and fork the block chain with it (XT) >=20 > There are no alternatives. People who object to (2) are inherently = suggesting (1) is the only acceptable path, which not surprisingly, = makes a lot of people very angry. It would be truly awesome to be able to give people more choice on = consensus rules. Unfortunately, cryptoledgers do not fork gracefully = (yet). Until we=E2=80=99re able to merge blockchain forks like we=E2=80=99= re able to merge git repo forks, the safest option is no fork. > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev --Apple-Mail=_35703E66-5314-4F38-9821-A1F71F7ECCBF 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""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div = class=3D"">On Jul 22, 2015, at 2:43 PM, Mike Hearn via bitcoin-dev = <<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" = class=3D"">bitcoin-dev@lists.linuxfoundation.org</a>> wrote:</div><br = class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" = class=3D"">Hi Pieter,<div class=3D""><br class=3D""></div><div = class=3D"">I think a core area of disagreement is this:<br 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"><p dir=3D"ltr" class=3D"">Bitcoin Core is not = running the Bitcoin economy, and its developers have no authority to set = its rules. </p></blockquote><div class=3D"">In fact Bitcoin Core is = running the Bitcoin economy, and its developers do have the authority to = set its rules. This is enforced by the reality of ~100% market share and = limited github commit access.</div><div class=3D""><br = class=3D""></div><div class=3D"">You may not like this situation, but it = is what it is. By refusing to make a release with different rules, = people who disagree are faced with only two options:</div><div = class=3D""><br class=3D""></div><div class=3D"">1. Swallow it even if = they hate it</div><div class=3D"">2. Fork the project and fork the block = chain with it (XT)</div><div class=3D""><br class=3D""></div><div = class=3D"">There are no alternatives. People who object to (2) are = inherently suggesting (1) is the only acceptable path, which not = surprisingly, makes a lot of people very = angry.</div></div></div></div></div></div></blockquote><div><br = class=3D""></div><div>It would be truly awesome to be able to give = people more choice on consensus rules. Unfortunately, cryptoledgers do = not fork gracefully (yet). 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><br class=3D""><blockquote type=3D"cite" class=3D""><div = class=3D""> _______________________________________________<br class=3D"">bitcoin-dev = mailing list<br class=3D""><a = href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" = class=3D"">bitcoin-dev@lists.linuxfoundation.org</a><br = class=3D"">https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev<= br class=3D""></div></blockquote></div><br class=3D""></body></html>= --Apple-Mail=_35703E66-5314-4F38-9821-A1F71F7ECCBF-- --Apple-Mail=_EBB0F521-9695-42FE-B827-549CD54A7319 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 iQIcBAEBCgAGBQJVsBGiAAoJEJNAI64YFENUsK0P/2WpT4W1OVqzNWiyfSxiPDrb odnLX+zu//yMxpkp1oFUND/zAvrGUkZ5e7peoXiiP/X4UZmbsLOhELQQnkZViOgy QyCKaYElxHXy37lv5XXjiG5Zinb1uVPZ8LpWI380Vw4QvJ8IJT6wISqN+RA7Kes7 UK8SIsI6zIy0D6NFOGT5lF9hoz2L9sMzDJJ+FQDys1W9m5pKpX+ShsDLu+WL9LFj 8bGRT/7Zrxa1u3FhsOk+qv9ePsVo9wMx6OloCbRZJxikb3Bt4Bq3aHkQ6xK5r/yb y5pGESbUQhuLmkdSCTUlnPMe8AJxa5KxFqdAPiwV6zQ65qsL7kdzUwixhQpiGGBd TlPP9CsdZvkdk4aNibEntSoWBewx1Csp0MrqWMDffw+zFWpqFh6gHdu2bfo4uItm CEvc2pnTyVPXg4fkqg9/HW1JFp6304+QYR4oplrv+0lrRkLxL+7XTHLE17RZzEaF TFflwz++SQQCHSxDWMmhS9ufkHMeHr20GUZ7y57u78ojv/CbT5U/zzg1u4Xu8lNW Vv12g4LjWqwbTIWXN1wC/j3ZObEDTlRuMKEzlJ7AqGw6QfQwOEo7TGCe04kN0B8j dKqvrn+z8oxF2r83jWf6Mu6HJc3S/1BJp6GZQljHmLBg0EYFPrIMH+T35/4GKnXW Gcqfi1M+IrXyIpZR/rBj =PNai -----END PGP SIGNATURE----- --Apple-Mail=_EBB0F521-9695-42FE-B827-549CD54A7319--