summaryrefslogtreecommitdiff
path: root/d2
diff options
context:
space:
mode:
authorJohn Hardy <john@seebitcoin.com>2017-07-05 09:18:36 +0000
committerbitcoindev <bitcoindev@gnusha.org>2017-07-05 09:21:42 +0000
commit1988d68a22cf7f1a271b3d9fddb50510dbffab3c (patch)
tree0fb4506b280371607467394415f751a51d6e0aa4 /d2
parent120ca6389867a829e32754ed097fd8bd77fb786e (diff)
downloadpi-bitcoindev-1988d68a22cf7f1a271b3d9fddb50510dbffab3c.tar.gz
pi-bitcoindev-1988d68a22cf7f1a271b3d9fddb50510dbffab3c.zip
[bitcoin-dev] The Nuclear Option: BIP148 + MR POWA
Diffstat (limited to 'd2')
-rw-r--r--d2/448f398d8307e34943c62e308745e62275adcf293
1 files changed, 293 insertions, 0 deletions
diff --git a/d2/448f398d8307e34943c62e308745e62275adcf b/d2/448f398d8307e34943c62e308745e62275adcf
new file mode 100644
index 000000000..bc1a8d325
--- /dev/null
+++ b/d2/448f398d8307e34943c62e308745e62275adcf
@@ -0,0 +1,293 @@
+Return-Path: <outlook_32F81FD1D1BD8CA0@outlook.com>
+Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
+ [172.17.192.35])
+ by mail.linuxfoundation.org (Postfix) with ESMTPS id 2983B5AC
+ for <bitcoin-dev@lists.linuxfoundation.org>;
+ Wed, 5 Jul 2017 09:21:42 +0000 (UTC)
+X-Greylist: whitelisted by SQLgrey-1.7.6
+Received: from NAM04-CO1-obe.outbound.protection.outlook.com
+ (mail-oln040092010068.outbound.protection.outlook.com [40.92.10.68])
+ by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 459B717E
+ for <bitcoin-dev@lists.linuxfoundation.org>;
+ Wed, 5 Jul 2017 09:21:41 +0000 (UTC)
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com;
+ s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version;
+ bh=pQcOn2Ci719FpyNd0lGLTolWPPfw0ewPd9Na/bpeW2A=;
+ b=uCfALFlqih2AanZqYPlnhgUKKbcU5RZ3sqf8Biaz2U7a4nQ1wpYFpVgE+CZOXPmFOAYMJxEcRV9oBY9i9qop+cSjngySO2QJJjvNEMJ9Rs9tpLImDBJ+8w48HHSOSjIsGkCv0QVm43xNm+uX+qx4MlDnPq8Tgc4uADC39HQ+gZBMkKz+MacjJchTxZyCVoTEDykNsLfn2oYvuRKyabEI2b70LFtTVhQpcPowrkcqCCXJ62RwtJUQ42andu1ZDFoLrV//p/FR4j4XeYonMjNCvOcKnioYi+ONVuE7Hu2zaZn54VbX/kqVEu1XZo1mIQYK2W4G/tIPPtQRYBkun7R2AA==
+Received: from CO1NAM04FT029.eop-NAM04.prod.protection.outlook.com
+ (10.152.90.57) by CO1NAM04HT139.eop-NAM04.prod.protection.outlook.com
+ (10.152.91.175) with Microsoft SMTP Server (version=TLS1_2,
+ cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1220.9;
+ Wed, 5 Jul 2017 09:18:37 +0000
+Received: from BLUPR0301MB2002.namprd03.prod.outlook.com (10.152.90.56) by
+ CO1NAM04FT029.mail.protection.outlook.com (10.152.90.172) with
+ Microsoft SMTP Server (version=TLS1_2,
+ cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id
+ 15.1.1220.9 via Frontend Transport; Wed, 5 Jul 2017 09:18:37 +0000
+Received: from BLUPR0301MB2002.namprd03.prod.outlook.com ([10.164.22.16]) by
+ BLUPR0301MB2002.namprd03.prod.outlook.com ([10.164.22.16]) with mapi id
+ 15.01.1220.018; Wed, 5 Jul 2017 09:18:36 +0000
+From: John Hardy <john@seebitcoin.com>
+To: "bitcoin-dev@lists.linuxfoundation.org"
+ <bitcoin-dev@lists.linuxfoundation.org>
+Thread-Topic: The Nuclear Option: BIP148 + MR POWA
+Thread-Index: AQHS9W156xx38V5whEGoVZoAIZwMKw==
+Sender: John Hardy <outlook_32F81FD1D1BD8CA0@outlook.com>
+Date: Wed, 5 Jul 2017 09:18:36 +0000
+Message-ID: <BLUPR0301MB200297FEF1BF16D950BCF981EED40@BLUPR0301MB2002.namprd03.prod.outlook.com>
+Accept-Language: en-US
+Content-Language: en-US
+X-MS-Has-Attach:
+X-MS-TNEF-Correlator:
+authentication-results: lists.linuxfoundation.org; dkim=none (message not
+ signed) header.d=none; lists.linuxfoundation.org; dmarc=none action=none
+ header.from=seebitcoin.com;
+x-incomingtopheadermarker: OriginalChecksum:638F8967A83404E20AEBB852381910FF7069601CA38BD72F73460E302586B7FF;
+ UpperCasedChecksum:40961A09BCB0533920D314A0406E8B53B4B063F960EACF9D7D11697981FE0B02;
+ SizeAsReceived:7135; Count:44
+x-ms-exchange-messagesentrepresentingtype: 2
+x-tmn: [iD3guWHeiXIRvJBdzd12h8qD7Ox9Gnz6]
+x-ms-publictraffictype: Email
+x-microsoft-exchange-diagnostics: 1; CO1NAM04HT139;
+ 7:pP9xHV1HYrPyjg2UU0U3YvTEsvkwZ7EhSofgpfIcT56spfNDA70/08o2igY5nIX/yblgUPrNdxkzTFL5xwLaWmFQ8QHR7mYrzWGrwIOfoZwYqxWWpl9U6c9MzyrdiGosHPBEXSmyWi2yA14IyVUANlhioQcnY/bP8fKsiWv3bCRjBYvfnwYulb5NNU+zWOpcde3I4yk8keTENf+74QueaiyiC6nD+AQhYepL4ci4iUef0Am7rNkLLNfiFtOrRtzOPaVTwra7psrPYZQ8rB//B9o1PxQ4t0ehiq5HxUpNu83r/43/pfFspSOppb5nXjycuplEHLWPK5aRREB3PxwX9Wea1sbs5sTLotkbBMx34WrnTs2F0Ql4HS7We4Pk+6ZtzLLh7bXoQyNMEsCWXBrM+ci19QH7GEIWDq+yBrNFXp7hXaQJPOmpQ0jKrVVeUVveGej51Ab41EafyAB1WtPKxYzt+0LtuRPTKdY5hc7O851gTDhste+KU8bZp7/chSmp//U2E8LuD+bt5w/G96eE+GMlILrfl4l0Cx+8gOcYyyWd9l2fOUBlIeAbolHprAdvIWzIHi105Ql7GvOeyCUSD734IiRirs5Tox2fRG1Nb/8HoYSTvhhODVX1KfkJoBWjOdecH6BS+gN2vavXziPLhhQqfF8RSgvk4wYBvTi4XsDEYDmFkvQst8Eliu89qCs09VzF15MPfTd0DPNji8nse9cN5dd9xbQ1faYWvl3yrwrsY4433ludi2ru1vaYahNjM72J5W5BnAO/gb8AML3xag==
+x-incomingheadercount: 44
+x-eopattributedmessage: 0
+x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004);
+ DIR:OUT; SFP:1901; SCL:1; SRVR:CO1NAM04HT139;
+ H:BLUPR0301MB2002.namprd03.prod.outlook.com; FPR:; SPF:None;
+ LANG:en;
+x-ms-office365-filtering-correlation-id: 067a04c1-f2bc-48bc-8f2d-08d4c386d136
+x-microsoft-antispam: UriScan:; BCL:0; PCL:0;
+ RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(300000503095)(300135400095)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1601125374)(1603101448)(1701031045)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095);
+ SRVR:CO1NAM04HT139;
+x-ms-traffictypediagnostic: CO1NAM04HT139:
+x-exchange-antispam-report-cfa-test: BCL:0; PCL:0;
+ RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(444000031);
+ SRVR:CO1NAM04HT139; BCL:0; PCL:0;
+ RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095);
+ SRVR:CO1NAM04HT139;
+x-forefront-prvs: 0359162B6D
+spamdiagnosticoutput: 1:99
+spamdiagnosticmetadata: NSPM
+Content-Type: multipart/alternative;
+ boundary="_000_BLUPR0301MB200297FEF1BF16D950BCF981EED40BLUPR0301MB2002_"
+MIME-Version: 1.0
+X-OriginatorOrg: outlook.com
+X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Jul 2017 09:18:36.5067 (UTC)
+X-MS-Exchange-CrossTenant-fromentityheader: Internet
+X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
+X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1NAM04HT139
+X-Spam-Status: No, score=-1.6 required=5.0 tests=BAYES_00,DKIM_SIGNED,
+ DKIM_VALID,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HTML_MESSAGE,
+ RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD autolearn=no version=3.3.1
+X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
+ smtp1.linux-foundation.org
+X-Mailman-Approved-At: Wed, 05 Jul 2017 13:20:08 +0000
+Subject: [bitcoin-dev] The Nuclear Option: BIP148 + MR POWA
+X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
+X-Mailman-Version: 2.1.12
+Precedence: list
+List-Id: Bitcoin Protocol 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, 05 Jul 2017 09:21:42 -0000
+
+--_000_BLUPR0301MB200297FEF1BF16D950BCF981EED40BLUPR0301MB2002_
+Content-Type: text/plain; charset="Windows-1252"
+Content-Transfer-Encoding: quoted-printable
+
+This idea is highly contentious as it would guarantee a viable chain of Bit=
+coin with SegWit activated whether BIP148 gained sufficient support or not.=
+ I am not necessarily advocating it - just putting it out for discussion. W=
+hile the downside is that it could permanently split the network, the upsid=
+e is that it could heap additional pressure on miners to follow the BIP148 =
+chain and ensure a minimally disruptive upgrade. This is pure game theory.
+
+
+
+MR POWA (Mining Reactive Proof of Work Addition) is a method to introduce a=
+n additional proof of work to a blockchain in response to a detected mining=
+ behaviour.
+
+
+
+In the case of BIP148, the criteria for activation could be when the softwa=
+re detects a non-BIP148 compliant chain that is 144 blocks (24 hours) ahead=
+ of a BIP148 compliant chain.
+
+
+
+At this stage the software would change its consensus rules (hard fork) to =
+do two things:
+
+ * Lower the difficulty for existing PoW method (SHA256).
+
+ * Introduce a second POW method, such as Scrypt or Ethash, that is inco=
+mpatible with SHA256 hardware but already has an established mining industr=
+y for altcoins.
+
+
+
+The difficulty should be low, and blocks will initially be found much more =
+quickly than every 10 minutes until the difficulty adjusts. Each method wou=
+ld have its own difficulty. It could be a requirement that POW methods alte=
+rnate to neutralise attacks from the other chain.
+
+
+
+This would guarantee SegWit activation. Anybody who is already running a BI=
+P148 node could just as easily run a BIP148 + MR POWA node. This could not =
+realistically be supported by Core and would have to be implemented in a gr=
+assroots movement, similar to BIP148.
+
+
+
+Ideally, it would just force the miners to follow the BIP148 chain (or risk=
+ the value of their hardware being hurt) and the code would never be activa=
+ted. MR POWA would mean BIP148 miners would no longer need to =93hold their=
+ nerve=94 as they would be guaranteed a viable chain and rewarded for their=
+ early support.
+
+
+Regards,
+
+
+John Hardy
+
+john@seebitcoin.com
+
+
+
+--_000_BLUPR0301MB200297FEF1BF16D950BCF981EED40BLUPR0301MB2002_
+Content-Type: text/html; charset="Windows-1252"
+Content-Transfer-Encoding: quoted-printable
+
+<html>
+<head>
+<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
+252">
+<style type=3D"text/css" style=3D"display:none;"><!-- P {margin-top:0;margi=
+n-bottom:0;} --></style>
+</head>
+<body dir=3D"ltr">
+<div id=3D"divtagdefaultwrapper" style=3D"font-size:12pt;color:#000000;font=
+-family:Calibri,Helvetica,sans-serif;" dir=3D"ltr">
+<p><span id=3D"docs-internal-guid-6c0fcb17-1202-79ea-96b2-c4a2764562bd"></s=
+pan></p>
+<p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt;"=
+><span style=3D"font-size: 11pt; font-family: Arial; background-color: tran=
+sparent; vertical-align: baseline; white-space: pre-wrap;">This idea is hig=
+hly contentious as it would guarantee
+ a viable chain of Bitcoin with SegWit activated whether BIP148 gained suff=
+icient support or not. I am not necessarily advocating it - just putting it=
+ out for discussion. While the downside is that it could permanently split =
+the network, the upside is that
+ it could heap additional pressure on miners to follow the BIP148 chain and=
+ ensure a minimally disruptive upgrade. This is pure game theory.</span></p=
+>
+<p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt;"=
+>&nbsp;</p>
+<p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt;"=
+><span style=3D"font-size: 11pt; font-family: Arial; background-color: tran=
+sparent; vertical-align: baseline; white-space: pre-wrap;">MR POWA (Mining =
+Reactive Proof of Work Addition) is a
+ method to introduce an additional proof of work to a blockchain in respons=
+e to a detected mining behaviour.</span></p>
+<p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt;"=
+>&nbsp;</p>
+<p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt;"=
+><span style=3D"font-size: 11pt; font-family: Arial; background-color: tran=
+sparent; vertical-align: baseline; white-space: pre-wrap;">In the case of B=
+IP148, the criteria for activation could
+ be when the software detects a non-BIP148 compliant chain that is 144 bloc=
+ks (24 hours) ahead of a BIP148 compliant chain.</span></p>
+<p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt;"=
+>&nbsp;</p>
+<p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt;"=
+><span style=3D"font-size: 11pt; font-family: Arial; background-color: tran=
+sparent; vertical-align: baseline; white-space: pre-wrap;">At this stage th=
+e software would change its consensus
+ rules (hard fork) to do two things:</span></p>
+<ul style=3D"margin-top:0pt;margin-bottom:0pt;">
+<li dir=3D"ltr" style=3D"list-style-type: disc; font-size: 11pt; font-famil=
+y: Arial; background-color: transparent; vertical-align: baseline;">
+<p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt;"=
+><span style=3D"font-size: 11pt; background-color: transparent; vertical-al=
+ign: baseline; white-space: pre-wrap;">Lower the difficulty for existing Po=
+W method (SHA256).</span></p>
+</li><li dir=3D"ltr" style=3D"list-style-type: disc; font-size: 11pt; font-=
+family: Arial; background-color: transparent; vertical-align: baseline;">
+<p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt;"=
+><span style=3D"font-size: 11pt; background-color: transparent; vertical-al=
+ign: baseline; white-space: pre-wrap;">Introduce a second POW method, such =
+as Scrypt or Ethash, that is incompatible
+ with SHA256 hardware but already has an established mining industry for al=
+tcoins.</span></p>
+</li></ul>
+<p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt;"=
+>&nbsp;</p>
+<p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt;"=
+><span style=3D"font-size: 11pt; font-family: Arial; background-color: tran=
+sparent; vertical-align: baseline; white-space: pre-wrap;">The difficulty s=
+hould be low, and blocks will initially
+ be found much more quickly than every 10 minutes until the difficulty adju=
+sts. Each method would have its own difficulty. It could be a requirement t=
+hat POW methods alternate to neutralise attacks from the other chain.</span=
+></p>
+<p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt;"=
+>&nbsp;</p>
+<p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt;"=
+><span style=3D"font-size: 11pt; font-family: Arial; background-color: tran=
+sparent; vertical-align: baseline; white-space: pre-wrap;">This would guara=
+ntee SegWit activation. Anybody who is
+ already running a BIP148 node could just as easily run a BIP148 &#43; MR P=
+OWA node. This could not realistically be supported by Core and would have =
+to be implemented in a grassroots movement, similar to BIP148.</span></p>
+<p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt;"=
+>&nbsp;</p>
+<p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt;"=
+><span style=3D"font-size: 11pt; font-family: Arial; background-color: tran=
+sparent; vertical-align: baseline; white-space: pre-wrap;">Ideally, it woul=
+d just force the miners to follow the
+ BIP148 chain<span style=3D"font-family: Arial; font-size: 14.6667px; white=
+-space: pre-wrap;"> (or risk the value of their hardware being hurt)</span>=
+ and the code would never be activated. MR POWA would mean BIP148 miners wo=
+uld no longer need to =93hold their
+ nerve=94 as they would be guaranteed a viable chain and rewarded for their=
+ early support.</span></p>
+<p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt;"=
+><span style=3D"font-size: 11pt; font-family: Arial; background-color: tran=
+sparent; vertical-align: baseline; white-space: pre-wrap;"><br>
+</span></p>
+<p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt;"=
+><span style=3D"font-size: 11pt; font-family: Arial; background-color: tran=
+sparent; vertical-align: baseline; white-space: pre-wrap;">Regards,</span><=
+/p>
+<p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt;"=
+><span style=3D"font-size: 11pt; font-family: Arial; background-color: tran=
+sparent; vertical-align: baseline; white-space: pre-wrap;"><br>
+</span></p>
+<p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt;"=
+><span style=3D"font-size: 11pt; font-family: Arial; background-color: tran=
+sparent; vertical-align: baseline; white-space: pre-wrap;">John Hardy</span=
+></p>
+<p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt;"=
+><span style=3D"font-size: 11pt; font-family: Arial; background-color: tran=
+sparent; vertical-align: baseline; white-space: pre-wrap;">john@seebitcoin.=
+com</span></p>
+<div><span style=3D"font-size: 11pt; font-family: Arial; background-color: =
+transparent; vertical-align: baseline; white-space: pre-wrap;"><br>
+</span></div>
+<br>
+<p></p>
+</div>
+</body>
+</html>
+
+--_000_BLUPR0301MB200297FEF1BF16D950BCF981EED40BLUPR0301MB2002_--
+