path: root/33/bcd2757049e51124d349ef2e6bd015a3ec340e

Return-Path: <jacob.eliosoff@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 8D6FFB5F
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed,  7 Jun 2017 04:17:41 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-lf0-f45.google.com (mail-lf0-f45.google.com
	[209.85.215.45])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 9837D213
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed,  7 Jun 2017 04:17:39 +0000 (UTC)
Received: by mail-lf0-f45.google.com with SMTP id o83so682240lff.3
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 06 Jun 2017 21:17:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc; bh=axbcz5qIzfZMTyY83cq5+PSUxfRDETFfOPZulSLdnbI=;
	b=Lqwd+Ps3U9n4AVrWQNFttiZakAhKkZfwLrhO8FYB+yYMkG9f1thJ8aeg5vzMH839lo
	Fkfx6qIKaLL82mMiUCiM96EP0FUS5Pa2SuZSb9BwQWuvisOczkORjXWc7QJrr1Bcyc1d
	mD3Yh4Va/sccIuU7cJ4iPoSMSaXzvQ9FazH/7ZAdjg4iQxctqKHZDLoocbURH7XNTQpV
	NZUbkFFGDyIZeIr9eVOuB/hA4VdURlx4tNFfBnVsLNPOmnyzxUz/AvYvKOYCdSqqeB8i
	gIjWJd8pitNKdWUNIPX7c0hRtbSstLnJB6NbWZJrZ3tqHxjQ72qwlQ21PVeduI1an732
	upyA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:cc;
	bh=axbcz5qIzfZMTyY83cq5+PSUxfRDETFfOPZulSLdnbI=;
	b=ViDF8HCIDsHs++6MoJ904sgWERzliprOb2FVWFWTyYmdSdK5hE4ogbMf1eP4ts5pf1
	6F+BLoD8zj07Ks+wUzEuA0JUGWP9pCHVSmfdThlIDezVKRaZitx2/CTQgK+xCIj6IuIl
	uBok7yT+0EQPW/2XLOOnRkJBcT8oXDTpc0Q+omh///wOM+IRwuPUT8TBmxvMniz1+SK8
	tZr5D3moCF3sfzNhMTfJxqPgWt/7otlYh+ZMDRILJLX619MNNa0ja1BslW3XLqatJFAJ
	utqOUQB/GiCcozTMfky5G+xiGLDkPfqyJfl9vUUlqlxIVvBxAko7zu8AgpRhkoGimwXX
	5ZxQ==
X-Gm-Message-State: AODbwcAVpKnf+WO2o+r6Ie930LgLrY3Y3YvCKfn8udwZay9gg9yXjxio
	H5KfvztRnKd8RrLJn8GMnfol2fZ8+A==
X-Received: by 10.25.18.154 with SMTP id 26mr7433647lfs.176.1496809057934;
	Tue, 06 Jun 2017 21:17:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.24.22 with HTTP; Tue, 6 Jun 2017 21:17:37 -0700 (PDT)
In-Reply-To: <CADvTj4q+oOS=DKfpiNQ6PAbksQfa1gKNfokr2Zc6PNGWqLyL4A@mail.gmail.com>
References: <CADvTj4qpH-t5Gx6qyn3yToyUE_GFaBE989=AWNHLKMpMNW3R+w@mail.gmail.com>
	<AE5BA251-9DA6-4E34-A748-11C8CF91977C@taoeffect.com>
	<CADvTj4q+oOS=DKfpiNQ6PAbksQfa1gKNfokr2Zc6PNGWqLyL4A@mail.gmail.com>
From: Jacob Eliosoff <jacob.eliosoff@gmail.com>
Date: Wed, 7 Jun 2017 00:17:37 -0400
Message-ID: <CAAUaCygpA896zWrcxysAose2e8ThYiBDKXu1LVwK22hmSXY11A@mail.gmail.com>
To: James Hilliard <james.hilliard1@gmail.com>
Content-Type: multipart/alternative; boundary="001a113fb3d431e5cb055157049a"
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
	RCVD_IN_DNSWL_NONE autolearn=ham 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, 07 Jun 2017 12:52:53 +0000
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] User Activated Soft Fork Split Protection
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, 07 Jun 2017 04:17:41 -0000

--001a113fb3d431e5cb055157049a
Content-Type: text/plain; charset="UTF-8"

While this isn't an unreasonable proposal, it will orphan blocks from any
miner who isn't running it (or BIP148) by Aug 1, right?  That seems rather
rushed for a non-backwards-compatible SF, especially since in practice,
miners are unlikely to deploy it until it comes bundled with some version
of the Segwit2x HF code.

I realize this is a touchy topic but - how much hard evidence is there that
there *will* be significant disruption if miners simply ignore both this
and BIP148?  Correct me but afaict, BIP148 has ~0% hashrate support.

Unless the HF code is ready and agree on soon (say by Jul 1), my vote is to
keep the main chain backwards-compatible, especially if evidence of miner
support for BIP148 doesn't materialize soon.  It seems less disruptive for
recently-deployed BIP148 nodes to revert than to ask every miner in the
system to quickly upgrade or get orphaned.

Just my view, I respect that others will differ.


On Tue, Jun 6, 2017 at 9:54 PM, James Hilliard via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> This is a BIP8 style soft fork so mandatory signalling will be active
> after Aug 1st regardless.
>
> On Tue, Jun 6, 2017 at 8:51 PM, Tao Effect <contact@taoeffect.com> wrote:
> > What is the probability that a 65% threshold is too low and can allow a
> > "surprise miner attack", whereby miners are kept offline before the
> > deadline, and brought online immediately after, creating potential havoc?
> >
> > (Nit: "simple majority" usually refers to >50%, I think, might cause
> > confusion.)
> >
> > -Greg Slepak
> >
> > --
> > Please do not email me anything that you are not comfortable also sharing
> > with the NSA.
> >
> > On Jun 6, 2017, at 5:56 PM, James Hilliard via bitcoin-dev
> > <bitcoin-dev@lists.linuxfoundation.org> wrote:
> >
> > Due to the proposed calendar(https://segwit2x.github.io/) for the
> > SegWit2x agreement being too slow to activate SegWit mandatory
> > signalling ahead of BIP148 using BIP91 I would like to propose another
> > option that miners can use to prevent a chain split ahead of the Aug
> > 1st BIP148 activation date.
> >
> > The splitprotection soft fork is essentially BIP91 but using BIP8
> > instead of BIP9 with a lower activation threshold and immediate
> > mandatory signalling lock-in. This allows for a majority of miners to
> > activate mandatory SegWit signalling and prevent a potential chain
> > split ahead of BIP148 activation.
> >
> > This BIP allows for miners to respond to market forces quickly ahead
> > of BIP148 activation by signalling for splitprotection. Any miners
> > already running BIP148 should be encouraged to use splitprotection.
> >
> > <pre>
> >  BIP: splitprotection
> >  Layer: Consensus (soft fork)
> >  Title: User Activated Soft Fork Split Protection
> >  Author: James Hilliard <james.hilliard1@gmail.com>
> >  Comments-Summary: No comments yet.
> >  Comments-URI:
> >  Status: Draft
> >  Type: Standards Track
> >  Created: 2017-05-22
> >  License: BSD-3-Clause
> >           CC0-1.0
> > </pre>
> >
> > ==Abstract==
> >
> > This document specifies a coordination mechanism for a simple majority
> > of miners to prevent a chain split ahead of BIP148 activation.
> >
> > ==Definitions==
> >
> > "existing segwit deployment" refer to the BIP9 "segwit" deployment
> > using bit 1, between November 15th 2016 and November 15th 2017 to
> > activate BIP141, BIP143 and BIP147.
> >
> > ==Motivation==
> >
> > The biggest risk of BIP148 is an extended chain split, this BIP
> > provides a way for a simple majority of miners to eliminate that risk.
> >
> > This BIP provides a way for a simple majority of miners to coordinate
> > activation of the existing segwit deployment with less than 95%
> > hashpower before BIP148 activation. Due to time constraints unless
> > immediately deployed BIP91 will likely not be able to enforce
> > mandatory signalling of segwit before the Aug 1st activation of
> > BIP148. This BIP provides a method for rapid miner activation of
> > SegWit mandatory signalling ahead of the BIP148 activation date. Since
> > the primary goal of this BIP is to reduce the chance of an extended
> > chain split as much as possible we activate using a simple miner
> > majority of 65% over a 504 block interval rather than a higher
> > percentage. This BIP also allows miners to signal their intention to
> > run BIP148 in order to prevent a chain split.
> >
> > ==Specification==
> >
> > While this BIP is active, all blocks must set the nVersion header top
> > 3 bits to 001 together with bit field (1<<1) (according to the
> > existing segwit deployment). Blocks that do not signal as required
> > will be rejected.
> >
> > ==Deployment==
> >
> > This BIP will be deployed by "version bits" with a 65%(this can be
> > adjusted if desired) activation threshold BIP9 with the name
> > "splitprotecion" and using bit 2.
> >
> > This BIP starts immediately and is a BIP8 style soft fork since
> > mandatory signalling will start on midnight August 1st 2017 (epoch
> > time 1501545600) regardless of whether or not this BIP has reached its
> > own signalling threshold. This BIP will cease to be active when segwit
> > is locked-in.
> >
> > === Reference implementation ===
> >
> > <pre>
> > // Check if Segregated Witness is Locked In
> > bool IsWitnessLockedIn(const CBlockIndex* pindexPrev, const
> > Consensus::Params& params)
> > {
> >    LOCK(cs_main);
> >    return (VersionBitsState(pindexPrev, params,
> > Consensus::DEPLOYMENT_SEGWIT, versionbitscache) ==
> > THRESHOLD_LOCKED_IN);
> > }
> >
> > // SPLITPROTECTION mandatory segwit signalling.
> > if ( VersionBitsState(pindex->pprev, chainparams.GetConsensus(),
> > Consensus::DEPLOYMENT_SPLITPROTECTION, versionbitscache) ==
> > THRESHOLD_LOCKED_IN &&
> >     !IsWitnessLockedIn(pindex->pprev, chainparams.GetConsensus()) &&
> > // Segwit is not locked in
> >     !IsWitnessEnabled(pindex->pprev, chainparams.GetConsensus()) ) //
> > and is not active.
> > {
> >    bool fVersionBits = (pindex->nVersion & VERSIONBITS_TOP_MASK) ==
> > VERSIONBITS_TOP_BITS;
> >    bool fSegbit = (pindex->nVersion &
> > VersionBitsMask(chainparams.GetConsensus(),
> > Consensus::DEPLOYMENT_SEGWIT)) != 0;
> >    if (!(fVersionBits && fSegbit)) {
> >        return state.DoS(0, error("ConnectBlock(): relayed block must
> > signal for segwit, please upgrade"), REJECT_INVALID, "bad-no-segwit");
> >    }
> > }
> >
> > // BIP148 mandatory segwit signalling.
> > int64_t nMedianTimePast = pindex->GetMedianTimePast();
> > if ( (nMedianTimePast >= 1501545600) &&  // Tue 01 Aug 2017 00:00:00 UTC
> >     (nMedianTimePast <= 1510704000) &&  // Wed 15 Nov 2017 00:00:00 UTC
> >     (!IsWitnessLockedIn(pindex->pprev, chainparams.GetConsensus()) &&
> > // Segwit is not locked in
> >      !IsWitnessEnabled(pindex->pprev, chainparams.GetConsensus())) )
> > // and is not active.
> > {
> >    bool fVersionBits = (pindex->nVersion & VERSIONBITS_TOP_MASK) ==
> > VERSIONBITS_TOP_BITS;
> >    bool fSegbit = (pindex->nVersion &
> > VersionBitsMask(chainparams.GetConsensus(),
> > Consensus::DEPLOYMENT_SEGWIT)) != 0;
> >    if (!(fVersionBits && fSegbit)) {
> >        return state.DoS(0, error("ConnectBlock(): relayed block must
> > signal for segwit, please upgrade"), REJECT_INVALID, "bad-no-segwit");
> >    }
> > }
> > </pre>
> >
> > https://github.com/bitcoin/bitcoin/compare/0.14...
> jameshilliard:splitprotection-v0.14.1
> >
> > ==Backwards Compatibility==
> >
> > This deployment is compatible with the existing "segwit" bit 1
> > deployment scheduled between midnight November 15th, 2016 and midnight
> > November 15th, 2017. This deployment is also compatible with the
> > existing BIP148 deployment. This BIP is compatible with BIP91 only if
> > BIP91 activates before it and before BIP148. Miners will need to
> > upgrade their nodes to support splitprotection otherwise they may
> > build on top of an invalid block. While this bip is active users
> > should either upgrade to splitprotection or wait for additional
> > confirmations when accepting payments.
> >
> > ==Rationale==
> >
> > Historically we have used IsSuperMajority() to activate soft forks
> > such as BIP66 which has a mandatory signalling requirement for miners
> > once activated, this ensures that miners are aware of new rules being
> > enforced. This technique can be leveraged to lower the signalling
> > threshold of a soft fork while it is in the process of being deployed
> > in a backwards compatible way. We also use a BIP8 style timeout to
> > ensure that this BIP is compatible with BIP148 and that BIP148
> > compatible mandatory signalling activates regardless of miner
> > signalling levels.
> >
> > By orphaning non-signalling blocks during the BIP9 bit 1 "segwit"
> > deployment, this BIP can cause the existing "segwit" deployment to
> > activate without needing to release a new deployment. As we approach
> > BIP148 activation it may be desirable for a majority of miners to have
> > a method that will ensure that there is no chain split.
> >
> > ==References==
> >
> > *[https://lists.linuxfoundation.org/pipermail/
> bitcoin-dev/2017-March/013714.html
> > Mailing list discussion]
> > *[https://github.com/bitcoin/bitcoin/blob/v0.6.0/src/main.
> cpp#L1281-L1283
> > P2SH flag day activation]
> > *[[bip-0009.mediawiki|BIP9 Version bits with timeout and delay]]
> > *[[bip-0016.mediawiki|BIP16 Pay to Script Hash]]
> > *[[bip-0091.mediawiki|BIP91 Reduced threshold Segwit MASF]]
> > *[[bip-0141.mediawiki|BIP141 Segregated Witness (Consensus layer)]]
> > *[[bip-0143.mediawiki|BIP143 Transaction Signature Verification for
> > Version 0 Witness Program]]
> > *[[bip-0147.mediawiki|BIP147 Dealing with dummy stack element
> malleability]]
> > *[[bip-0148.mediawiki|BIP148 Mandatory activation of segwit deployment]]
> > *[[bip-0149.mediawiki|BIP149 Segregated Witness (second deployment)]]
> > *[https://bitcoincore.org/en/2016/01/26/segwit-benefits/ Segwit
> benefits]
> >
> > ==Copyright==
> >
> > This document is dual licensed as BSD 3-clause, and Creative Commons
> > CC0 1.0 Universal.
> > _______________________________________________
> > bitcoin-dev mailing list
> > bitcoin-dev@lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> >
> >
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

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

<div dir=3D"ltr">While this isn&#39;t an unreasonable proposal, it will orp=
han blocks from any miner who isn&#39;t running it (or BIP148) by Aug 1, ri=
ght?=C2=A0 That seems rather rushed for a non-backwards-compatible SF, espe=
cially since in practice, miners are unlikely to deploy it until it comes b=
undled with some version of the Segwit2x HF code.<div><br></div><div>I real=
ize this is a touchy topic but - how much hard evidence is there that there=
 *will* be significant disruption if miners simply ignore both this and BIP=
148?=C2=A0 Correct me but afaict, BIP148 has ~0% hashrate support.</div><di=
v><br></div><div>Unless the HF code is ready and agree on soon (say by Jul =
1), my vote is to keep the main chain backwards-compatible, especially if e=
vidence of miner support for BIP148 doesn&#39;t materialize soon.=C2=A0 It =
seems less disruptive for recently-deployed BIP148 nodes to revert than to =
ask every miner in the system to quickly upgrade or get orphaned.</div><div=
><br></div><div>Just my view, I respect that others will differ.<br></div><=
div><br></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quot=
e">On Tue, Jun 6, 2017 at 9:54 PM, James Hilliard via bitcoin-dev <span dir=
=3D"ltr">&lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" targe=
t=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">This is a BIP8 style soft fork so mandatory=
 signalling will be active<br>
after Aug 1st regardless.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
On Tue, Jun 6, 2017 at 8:51 PM, Tao Effect &lt;<a href=3D"mailto:contact@ta=
oeffect.com">contact@taoeffect.com</a>&gt; wrote:<br>
&gt; What is the probability that a 65% threshold is too low and can allow =
a<br>
&gt; &quot;surprise miner attack&quot;, whereby miners are kept offline bef=
ore the<br>
&gt; deadline, and brought online immediately after, creating potential hav=
oc?<br>
&gt;<br>
&gt; (Nit: &quot;simple majority&quot; usually refers to &gt;50%, I think, =
might cause<br>
&gt; confusion.)<br>
&gt;<br>
&gt; -Greg Slepak<br>
&gt;<br>
&gt; --<br>
&gt; Please do not email me anything that you are not comfortable also shar=
ing<br>
&gt; with the NSA.<br>
&gt;<br>
&gt; On Jun 6, 2017, at 5:56 PM, James Hilliard via bitcoin-dev<br>
&gt; &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-d=
ev@lists.<wbr>linuxfoundation.org</a>&gt; wrote:<br>
&gt;<br>
&gt; Due to the proposed calendar(<a href=3D"https://segwit2x.github.io/" r=
el=3D"noreferrer" target=3D"_blank">https://segwit2x.<wbr>github.io/</a>) f=
or the<br>
&gt; SegWit2x agreement being too slow to activate SegWit mandatory<br>
&gt; signalling ahead of BIP148 using BIP91 I would like to propose another=
<br>
&gt; option that miners can use to prevent a chain split ahead of the Aug<b=
r>
&gt; 1st BIP148 activation date.<br>
&gt;<br>
&gt; The splitprotection soft fork is essentially BIP91 but using BIP8<br>
&gt; instead of BIP9 with a lower activation threshold and immediate<br>
&gt; mandatory signalling lock-in. This allows for a majority of miners to<=
br>
&gt; activate mandatory SegWit signalling and prevent a potential chain<br>
&gt; split ahead of BIP148 activation.<br>
&gt;<br>
&gt; This BIP allows for miners to respond to market forces quickly ahead<b=
r>
&gt; of BIP148 activation by signalling for splitprotection. Any miners<br>
&gt; already running BIP148 should be encouraged to use splitprotection.<br=
>
&gt;<br>
&gt; &lt;pre&gt;<br>
&gt;=C2=A0 BIP: splitprotection<br>
&gt;=C2=A0 Layer: Consensus (soft fork)<br>
&gt;=C2=A0 Title: User Activated Soft Fork Split Protection<br>
&gt;=C2=A0 Author: James Hilliard &lt;<a href=3D"mailto:james.hilliard1@gma=
il.com">james.hilliard1@gmail.com</a>&gt;<br>
&gt;=C2=A0 Comments-Summary: No comments yet.<br>
&gt;=C2=A0 Comments-URI:<br>
&gt;=C2=A0 Status: Draft<br>
&gt;=C2=A0 Type: Standards Track<br>
&gt;=C2=A0 Created: 2017-05-22<br>
&gt;=C2=A0 License: BSD-3-Clause<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0CC0-1.0<br>
&gt; &lt;/pre&gt;<br>
&gt;<br>
&gt; =3D=3DAbstract=3D=3D<br>
&gt;<br>
&gt; This document specifies a coordination mechanism for a simple majority=
<br>
&gt; of miners to prevent a chain split ahead of BIP148 activation.<br>
&gt;<br>
&gt; =3D=3DDefinitions=3D=3D<br>
&gt;<br>
&gt; &quot;existing segwit deployment&quot; refer to the BIP9 &quot;segwit&=
quot; deployment<br>
&gt; using bit 1, between November 15th 2016 and November 15th 2017 to<br>
&gt; activate BIP141, BIP143 and BIP147.<br>
&gt;<br>
&gt; =3D=3DMotivation=3D=3D<br>
&gt;<br>
&gt; The biggest risk of BIP148 is an extended chain split, this BIP<br>
&gt; provides a way for a simple majority of miners to eliminate that risk.=
<br>
&gt;<br>
&gt; This BIP provides a way for a simple majority of miners to coordinate<=
br>
&gt; activation of the existing segwit deployment with less than 95%<br>
&gt; hashpower before BIP148 activation. Due to time constraints unless<br>
&gt; immediately deployed BIP91 will likely not be able to enforce<br>
&gt; mandatory signalling of segwit before the Aug 1st activation of<br>
&gt; BIP148. This BIP provides a method for rapid miner activation of<br>
&gt; SegWit mandatory signalling ahead of the BIP148 activation date. Since=
<br>
&gt; the primary goal of this BIP is to reduce the chance of an extended<br=
>
&gt; chain split as much as possible we activate using a simple miner<br>
&gt; majority of 65% over a 504 block interval rather than a higher<br>
&gt; percentage. This BIP also allows miners to signal their intention to<b=
r>
&gt; run BIP148 in order to prevent a chain split.<br>
&gt;<br>
&gt; =3D=3DSpecification=3D=3D<br>
&gt;<br>
&gt; While this BIP is active, all blocks must set the nVersion header top<=
br>
&gt; 3 bits to 001 together with bit field (1&lt;&lt;1) (according to the<b=
r>
&gt; existing segwit deployment). Blocks that do not signal as required<br>
&gt; will be rejected.<br>
&gt;<br>
&gt; =3D=3DDeployment=3D=3D<br>
&gt;<br>
&gt; This BIP will be deployed by &quot;version bits&quot; with a 65%(this =
can be<br>
&gt; adjusted if desired) activation threshold BIP9 with the name<br>
&gt; &quot;splitprotecion&quot; and using bit 2.<br>
&gt;<br>
&gt; This BIP starts immediately and is a BIP8 style soft fork since<br>
&gt; mandatory signalling will start on midnight August 1st 2017 (epoch<br>
&gt; time 1501545600) regardless of whether or not this BIP has reached its=
<br>
&gt; own signalling threshold. This BIP will cease to be active when segwit=
<br>
&gt; is locked-in.<br>
&gt;<br>
&gt; =3D=3D=3D Reference implementation =3D=3D=3D<br>
&gt;<br>
&gt; &lt;pre&gt;<br>
&gt; // Check if Segregated Witness is Locked In<br>
&gt; bool IsWitnessLockedIn(const CBlockIndex* pindexPrev, const<br>
&gt; Consensus::Params&amp; params)<br>
&gt; {<br>
&gt;=C2=A0 =C2=A0 LOCK(cs_main);<br>
&gt;=C2=A0 =C2=A0 return (VersionBitsState(pindexPrev, params,<br>
&gt; Consensus::DEPLOYMENT_SEGWIT, versionbitscache) =3D=3D<br>
&gt; THRESHOLD_LOCKED_IN);<br>
&gt; }<br>
&gt;<br>
&gt; // SPLITPROTECTION mandatory segwit signalling.<br>
&gt; if ( VersionBitsState(pindex-&gt;<wbr>pprev, chainparams.GetConsensus(=
),<br>
&gt; Consensus::DEPLOYMENT_<wbr>SPLITPROTECTION, versionbitscache) =3D=3D<b=
r>
&gt; THRESHOLD_LOCKED_IN &amp;&amp;<br>
&gt;=C2=A0 =C2=A0 =C2=A0!IsWitnessLockedIn(pindex-&gt;<wbr>pprev, chainpara=
ms.GetConsensus()) &amp;&amp;<br>
&gt; // Segwit is not locked in<br>
&gt;=C2=A0 =C2=A0 =C2=A0!IsWitnessEnabled(pindex-&gt;<wbr>pprev, chainparam=
s.GetConsensus()) ) //<br>
&gt; and is not active.<br>
&gt; {<br>
&gt;=C2=A0 =C2=A0 bool fVersionBits =3D (pindex-&gt;nVersion &amp; VERSIONB=
ITS_TOP_MASK) =3D=3D<br>
&gt; VERSIONBITS_TOP_BITS;<br>
&gt;=C2=A0 =C2=A0 bool fSegbit =3D (pindex-&gt;nVersion &amp;<br>
&gt; VersionBitsMask(chainparams.<wbr>GetConsensus(),<br>
&gt; Consensus::DEPLOYMENT_SEGWIT)) !=3D 0;<br>
&gt;=C2=A0 =C2=A0 if (!(fVersionBits &amp;&amp; fSegbit)) {<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 return state.DoS(0, error(&quot;ConnectBloc=
k(): relayed block must<br>
&gt; signal for segwit, please upgrade&quot;), REJECT_INVALID, &quot;bad-no=
-segwit&quot;);<br>
&gt;=C2=A0 =C2=A0 }<br>
&gt; }<br>
&gt;<br>
&gt; // BIP148 mandatory segwit signalling.<br>
&gt; int64_t nMedianTimePast =3D pindex-&gt;GetMedianTimePast();<br>
&gt; if ( (nMedianTimePast &gt;=3D 1501545600) &amp;&amp;=C2=A0 // Tue 01 A=
ug 2017 00:00:00 UTC<br>
&gt;=C2=A0 =C2=A0 =C2=A0(nMedianTimePast &lt;=3D 1510704000) &amp;&amp;=C2=
=A0 // Wed 15 Nov 2017 00:00:00 UTC<br>
&gt;=C2=A0 =C2=A0 =C2=A0(!IsWitnessLockedIn(pindex-&gt;<wbr>pprev, chainpar=
ams.GetConsensus()) &amp;&amp;<br>
&gt; // Segwit is not locked in<br>
&gt;=C2=A0 =C2=A0 =C2=A0 !IsWitnessEnabled(pindex-&gt;<wbr>pprev, chainpara=
ms.GetConsensus())) )<br>
&gt; // and is not active.<br>
&gt; {<br>
&gt;=C2=A0 =C2=A0 bool fVersionBits =3D (pindex-&gt;nVersion &amp; VERSIONB=
ITS_TOP_MASK) =3D=3D<br>
&gt; VERSIONBITS_TOP_BITS;<br>
&gt;=C2=A0 =C2=A0 bool fSegbit =3D (pindex-&gt;nVersion &amp;<br>
&gt; VersionBitsMask(chainparams.<wbr>GetConsensus(),<br>
&gt; Consensus::DEPLOYMENT_SEGWIT)) !=3D 0;<br>
&gt;=C2=A0 =C2=A0 if (!(fVersionBits &amp;&amp; fSegbit)) {<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 return state.DoS(0, error(&quot;ConnectBloc=
k(): relayed block must<br>
&gt; signal for segwit, please upgrade&quot;), REJECT_INVALID, &quot;bad-no=
-segwit&quot;);<br>
&gt;=C2=A0 =C2=A0 }<br>
&gt; }<br>
&gt; &lt;/pre&gt;<br>
&gt;<br>
&gt; <a href=3D"https://github.com/bitcoin/bitcoin/compare/0.14...jameshill=
iard:splitprotection-v0.14.1" rel=3D"noreferrer" target=3D"_blank">https://=
github.com/bitcoin/<wbr>bitcoin/compare/0.14...<wbr>jameshilliard:splitprot=
ection-<wbr>v0.14.1</a><br>
&gt;<br>
&gt; =3D=3DBackwards Compatibility=3D=3D<br>
&gt;<br>
&gt; This deployment is compatible with the existing &quot;segwit&quot; bit=
 1<br>
&gt; deployment scheduled between midnight November 15th, 2016 and midnight=
<br>
&gt; November 15th, 2017. This deployment is also compatible with the<br>
&gt; existing BIP148 deployment. This BIP is compatible with BIP91 only if<=
br>
&gt; BIP91 activates before it and before BIP148. Miners will need to<br>
&gt; upgrade their nodes to support splitprotection otherwise they may<br>
&gt; build on top of an invalid block. While this bip is active users<br>
&gt; should either upgrade to splitprotection or wait for additional<br>
&gt; confirmations when accepting payments.<br>
&gt;<br>
&gt; =3D=3DRationale=3D=3D<br>
&gt;<br>
&gt; Historically we have used IsSuperMajority() to activate soft forks<br>
&gt; such as BIP66 which has a mandatory signalling requirement for miners<=
br>
&gt; once activated, this ensures that miners are aware of new rules being<=
br>
&gt; enforced. This technique can be leveraged to lower the signalling<br>
&gt; threshold of a soft fork while it is in the process of being deployed<=
br>
&gt; in a backwards compatible way. We also use a BIP8 style timeout to<br>
&gt; ensure that this BIP is compatible with BIP148 and that BIP148<br>
&gt; compatible mandatory signalling activates regardless of miner<br>
&gt; signalling levels.<br>
&gt;<br>
&gt; By orphaning non-signalling blocks during the BIP9 bit 1 &quot;segwit&=
quot;<br>
&gt; deployment, this BIP can cause the existing &quot;segwit&quot; deploym=
ent to<br>
&gt; activate without needing to release a new deployment. As we approach<b=
r>
&gt; BIP148 activation it may be desirable for a majority of miners to have=
<br>
&gt; a method that will ensure that there is no chain split.<br>
&gt;<br>
&gt; =3D=3DReferences=3D=3D<br>
&gt;<br>
&gt; *[<a href=3D"https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2=
017-March/013714.html" rel=3D"noreferrer" target=3D"_blank">https://lists.<=
wbr>linuxfoundation.org/pipermail/<wbr>bitcoin-dev/2017-March/013714.<wbr>h=
tml</a><br>
&gt; Mailing list discussion]<br>
&gt; *[<a href=3D"https://github.com/bitcoin/bitcoin/blob/v0.6.0/src/main.c=
pp#L1281-L1283" rel=3D"noreferrer" target=3D"_blank">https://github.com/bit=
coin/<wbr>bitcoin/blob/v0.6.0/src/main.<wbr>cpp#L1281-L1283</a><br>
&gt; P2SH flag day activation]<br>
&gt; *[[bip-0009.mediawiki|BIP9 Version bits with timeout and delay]]<br>
&gt; *[[bip-0016.mediawiki|BIP16 Pay to Script Hash]]<br>
&gt; *[[bip-0091.mediawiki|BIP91 Reduced threshold Segwit MASF]]<br>
&gt; *[[bip-0141.mediawiki|BIP141 Segregated Witness (Consensus layer)]]<br=
>
&gt; *[[bip-0143.mediawiki|BIP143 Transaction Signature Verification for<br=
>
&gt; Version 0 Witness Program]]<br>
&gt; *[[bip-0147.mediawiki|BIP147 Dealing with dummy stack element malleabi=
lity]]<br>
&gt; *[[bip-0148.mediawiki|BIP148 Mandatory activation of segwit deployment=
]]<br>
&gt; *[[bip-0149.mediawiki|BIP149 Segregated Witness (second deployment)]]<=
br>
&gt; *[<a href=3D"https://bitcoincore.org/en/2016/01/26/segwit-benefits/" r=
el=3D"noreferrer" target=3D"_blank">https://bitcoincore.org/en/<wbr>2016/01=
/26/segwit-benefits/</a> Segwit benefits]<br>
&gt;<br>
&gt; =3D=3DCopyright=3D=3D<br>
&gt;<br>
&gt; This document is dual licensed as BSD 3-clause, and Creative Commons<b=
r>
&gt; CC0 1.0 Universal.<br>
&gt; ______________________________<wbr>_________________<br>
&gt; bitcoin-dev mailing list<br>
&gt; <a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@l=
ists.<wbr>linuxfoundation.org</a><br>
&gt; <a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-=
dev" rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.<wb=
r>org/mailman/listinfo/bitcoin-<wbr>dev</a><br>
&gt;<br>
&gt;<br>
______________________________<wbr>_________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
<wbr>linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.<wbr>org=
/mailman/listinfo/bitcoin-<wbr>dev</a><br>
</div></div></blockquote></div><br></div>

--001a113fb3d431e5cb055157049a--