path: root/dd/dc7ecc906bbc786950952af907f95c113aae3e

Return-Path: <ben.woosley@gmail.com>
Received: from smtp1.osuosl.org (smtp1.osuosl.org [IPv6:2605:bc80:3010::138])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 642D1C000A
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Thu,  1 Apr 2021 18:06:01 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp1.osuosl.org (Postfix) with ESMTP id 45E1684A18
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Thu,  1 Apr 2021 18:06:01 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: 1.602
X-Spam-Level: *
X-Spam-Status: No, score=1.602 tagged_above=-999 required=5
 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
 FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001,
 SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: smtp1.osuosl.org (amavisd-new);
 dkim=pass (2048-bit key) header.d=gmail.com
Received: from smtp1.osuosl.org ([127.0.0.1])
 by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 9won2F4gNQSI
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Thu,  1 Apr 2021 18:05:57 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
Received: from mail-wr1-x42f.google.com (mail-wr1-x42f.google.com
 [IPv6:2a00:1450:4864:20::42f])
 by smtp1.osuosl.org (Postfix) with ESMTPS id E520584A0E
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Thu,  1 Apr 2021 18:05:56 +0000 (UTC)
Received: by mail-wr1-x42f.google.com with SMTP id x7so2664649wrw.10
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Thu, 01 Apr 2021 11:05:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
 h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
 bh=yCJlW8019dMZBagtdCCIUTXisMCaS1Q1+wmRm+ui/kM=;
 b=Zk0GMfo+FgC8f3rFvTCMum8TtduPFXYu2HiJadnUaY9u86djKk8YYUgzBp+6bnxTSe
 1dUd+xMQLIj8/PImNbwQmw5ZNuX/PzpfVvzpeNSCNbHLQyDiHzCp1HD4u9bvuQ0pCbAe
 xKac/pVhZV+j7sjR9AW9aFtQOZXKetkDiodg2Mspg6sPE91k8vVvq7NnLC4l90ic86at
 ykvGRDevytMlKXr2EkEx5LL0g5sUdVB4bosPSMMukdlONRraJBGbB7YBckja6zqJRDBv
 ov2opv4CNScFeGz8wteChfu3PrMkrnFl4XRpspPUvSjgNhLzl6I2iT3D+JL6VWE30Rfj
 G1kQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to;
 bh=yCJlW8019dMZBagtdCCIUTXisMCaS1Q1+wmRm+ui/kM=;
 b=tTQCD88cmJPoFQpOLyXRzPLkUY9q0bnFsYzbl3G916hECLVqgebZvD8ADpS0Jf6/5y
 NxXx3ShFL9dIfpc8LUGtmtCPqELEFW+VFH355Csb7EGMJjf7k+uaxDhe8ifkltoFqBm9
 R0YBbrnFctE0tnW4xL8Kb5zWk/8QhL//hYeW6b/bYAFgYsRKuv3hiidMtxzzDYC+et+O
 ZZxSPTdFksDa2oaB2SJvcjOBXLuC4kWJB36R5bIShgygvKh/4kO9xhdow/wLXR+Sj+JR
 ABrhFpCEGEuHvLUpSJgBxCGB+hGThjzDT2GL9pf8Pu8ZsUhBNIoyc4cpbrduGVeuwmmA
 GM1A==
X-Gm-Message-State: AOAM532637QlCouH0Q0rSeveJirbOBO7syPzjL4U/8P+036VmfQmQfmY
 kGhfpxVggBWArFxwlg6Z3ZE4ZaN0XAZGly2rjLM=
X-Google-Smtp-Source: ABdhPJzbn7bhBM4jCgX0FSc3amtsf+MeMJoKMbs54it3WWBXzcOR8YaLvmg0U3eQ1WxKXVlKMQGZqNm36dLcKVlnkWI=
X-Received: by 2002:a05:6000:11c1:: with SMTP id
 i1mr11086225wrx.215.1617300354951; 
 Thu, 01 Apr 2021 11:05:54 -0700 (PDT)
MIME-Version: 1.0
References: <CAFvNmHSO1qBv2Lm4uHq82oEx5nxayKRsyP3Vx6BNfHJiOaztPQ@mail.gmail.com>
In-Reply-To: <CAFvNmHSO1qBv2Lm4uHq82oEx5nxayKRsyP3Vx6BNfHJiOaztPQ@mail.gmail.com>
From: Ben Woosley <ben.woosley@gmail.com>
Date: Thu, 1 Apr 2021 11:05:28 -0700
Message-ID: <CAC5gnOyeg78ASZmQiDJMf2v8p50OqSBBH_FUSs79qaDVLR5Teg@mail.gmail.com>
To: Michael Folkson <michaelfolkson@gmail.com>, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="00000000000026ef7a05beed1599"
X-Mailman-Approved-At: Mon, 05 Apr 2021 21:47:48 +0000
Subject: Re: [bitcoin-dev] Announcing a new standard for soft fork activation
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
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: Thu, 01 Apr 2021 18:06:01 -0000

--00000000000026ef7a05beed1599
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hear hear, a true work of genius. Who's looking for Satoshi? I think we've
found him!

On Thu, Apr 1, 2021 at 8:15 AM Michael Folkson via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> There have been a vast number of proposals for soft fork activation in
> recent months and it is important that all these important ideas don=E2=
=80=99t go
> to waste. Hence I propose a new standard for soft fork activation
> incorporating all the ideas into one standard. I appreciate this standard
> has come too late for Taproot activation but it should be ready for any
> future soft forks. It is a multi phase, multi year standard. No soft fork
> can activate unless and until it has successfully passed through all of t=
he
> different 14 phases. This will demonstrate Bitcoin=E2=80=99s ultimate con=
servatism.
>
> Phase 1) Let=E2=80=99s See What Happens - BIP 8 (false, 0.25 years). The =
shortest
> phase just to whet appetites.
>
> Phase 2) Start now, improve later - BIP 8(false, 1 year) A confusing name=
,
> it starts but it doesn't improve later
>
> Phase 3) BIP 9 equivalent - BIP 8(false, 1 year)
>
> Phase 4) Gently discourage apathy - BIP 8(true, 1 year) Forced signaling
> at the end of this phase but obviously there are still many phases before
> the soft fork can actually activate.
>
> Phase 5) BIP 91 (1 year). As a nod to our SegWit history we have a BIP 91
> activation phase.
>
> Phase 6) BIP 148 (1 year). Some people disagree that BIP 91 activated
> SegWit so we do a BIP 148 activation phase to keep those people happy.
> Again forced signaling doesn=E2=80=99t actually mean activation. There ar=
e still
> many more phases to pass through.
>
> Phase 7) Speedy Trial (using block height, 0.5 years) on mainnet
>
> Phase 8) Speedy Trial (using MTP, 0.5 years) on mainnet
>
> Phase 9) Speedy Trial on the default signet (0.5 years)
>
> Phase 10) Speedy Trial on a combination of three different custom signets
> in parallel (0.5 years)
>
> Phase 11) Speedy Trial on testnet and a custom signet in parallel (0.5
> years)
>
> Phase 12) Modern Soft Fork Activation (3.5 years) This is the longest
> phase of the soft fork activation standard. It is itself multi phase and
> multi year so this can be considered a nested activation phase within thi=
s
> standard.
>
> Phase 13) UASF BIP 8 (LOT=3Dtrue, 1 year). Forced miner signaling at the =
end
> of this phase but ultimately the soft fork doesn=E2=80=99t yet activate a=
s there is
> one final additional phase the activation must pass through. This gives
> Samson the opportunity to sell some hats. We are close now. The natives a=
re
> getting restless.
>
> Phase 14) Second flag day (1 year) We don=E2=80=99t want those pesky user=
s
> actually activating a soft fork on their own so an additional flag day is
> added just so we can tell users that we prevented a chain split.
>
> Assuming a soft fork activation has successfully passed through all these
> 14 phases it should activate. It will take a minimum of 13 years. However=
,
> if it fails during any one of these phases it has to start from Phase 1
> again. We should take Bitcoin=E2=80=99s conservatism very seriously. If a=
 soft fork
> activation can=E2=80=99t pass successfully through all these phases it sh=
ouldn=E2=80=99t
> activate. Ultimately we don=E2=80=99t really mind what is in the soft for=
k (any
> idiot can design consensus changes and write secure bug free C++ code) th=
at
> is very much secondary in importance to *how* the soft fork is activated.
> The activation design absolutely must be conservative.
>
> I expect this rigorous standard for soft fork activation will get a BIP
> number. If you are going to propose a future soft fork I recommend you pl=
an
> for activation in approximately 13 years from the point the soft fork cod=
e
> is merged into Core.
>
> I am happy to settle the soft fork activation question once and for all
> for the community. I expect in time my contribution will be recognized in
> the annals of history with Satoshi Nakamoto and Hal Finney.
>
> Addendum: Although all future soft forks will ultimately use this
> standard, this standard is copyrighted. Every time it is used royalties
> must be paid into this quantum secure Bitcoin vanity address
> 1quantumsecureaddress
>
>
> --
> Michael Folkson
> Email: michaelfolkson@gmail.com
> Keybase: michaelfolkson
> PGP: 43ED C999 9F85 1D40 EAF4 9835 92D6 0159 214C FEE3
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

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

<div dir=3D"ltr">Hear hear, a true work of genius. Who&#39;s looking for Sa=
toshi? I think we&#39;ve found him!</div><br><div class=3D"gmail_quote"><di=
v dir=3D"ltr" class=3D"gmail_attr">On Thu, Apr 1, 2021 at 8:15 AM Michael F=
olkson via bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundat=
ion.org">bitcoin-dev@lists.linuxfoundation.org</a>&gt; wrote:<br></div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);paddi=
ng-left:1ex"><div dir=3D"ltr">There have been a vast number of proposals fo=
r soft fork activation in recent months and it is important that all these =
important ideas don=E2=80=99t go to waste. Hence I propose a new standard f=
or soft fork activation incorporating all the ideas into one standard. I ap=
preciate this standard has come too late for Taproot activation but it shou=
ld be ready for any future soft forks. It is a multi phase, multi year stan=
dard. No soft fork can activate unless and until it has successfully passed=
 through all of the different 14 phases. This will demonstrate Bitcoin=E2=
=80=99s ultimate conservatism.<br><br><div>Phase 1) Let=E2=80=99s See What =
Happens - BIP 8 (false, 0.25 years). The shortest phase just to whet appeti=
tes.<br><br></div><div>Phase 2) Start now, improve later - BIP 8(false, 1 y=
ear) A confusing name, it starts but it doesn&#39;t improve later<br><br></=
div><div>Phase 3) BIP 9 equivalent - BIP 8(false, 1 year)<br><br></div><div=
>Phase 4) Gently discourage apathy - BIP 8(true, 1 year) Forced signaling a=
t the end of this phase but obviously there are still many phases before th=
e soft fork can actually activate.<br><br></div><div>Phase 5) BIP 91 (1 yea=
r). As a nod to our SegWit history we have a BIP 91 activation phase.<br><b=
r></div><div>Phase 6) BIP 148 (1 year). Some people disagree that BIP 91 ac=
tivated SegWit so we do a BIP 148 activation phase to keep those people hap=
py. Again forced signaling doesn=E2=80=99t actually mean activation. There =
are still many more phases to pass through.<br><br></div><div>Phase 7) Spee=
dy Trial (using block height, 0.5 years) on mainnet<br><br></div><div>Phase=
 8) Speedy Trial (using MTP, 0.5 years) on mainnet<br><br></div><div>Phase =
9) Speedy Trial on the default signet (0.5 years)<br><br></div><div>Phase 1=
0) Speedy Trial on a combination of three different custom signets in paral=
lel (0.5 years)<br><br></div><div>Phase 11) Speedy Trial on testnet and a c=
ustom signet in parallel (0.5 years)<br><br></div><div>Phase 12) Modern Sof=
t Fork Activation (3.5 years) This is the longest phase of the soft fork ac=
tivation standard. It is itself multi phase and multi year so this can be c=
onsidered a nested activation phase within this standard.<br><br></div><div=
>Phase 13) UASF BIP 8 (LOT=3Dtrue, 1 year). Forced miner signaling at the e=
nd of this phase but ultimately the soft fork doesn=E2=80=99t yet activate =
as there is one final additional phase the activation must pass through. Th=
is gives Samson the opportunity to sell some hats. We are close now. The na=
tives are getting restless.<br><br></div><div>Phase 14) Second flag day (1 =
year) We don=E2=80=99t want those pesky users actually activating a soft fo=
rk on their own so an additional flag day is added just so we can tell user=
s that we prevented a chain split. <br><br></div><div>Assuming a soft fork =
activation has successfully passed through all these 14 phases it should ac=
tivate. It will take a minimum of 13 years. However, if it fails during any=
 one of these phases it has to start from Phase 1 again. We should take Bit=
coin=E2=80=99s conservatism very seriously. If a soft fork activation can=
=E2=80=99t pass successfully through all these phases it shouldn=E2=80=99t =
activate. Ultimately we don=E2=80=99t really mind what is in the soft fork =
(any idiot can design consensus changes and write secure bug free C++ code)=
 that is very much secondary in importance to *how* the soft fork is activa=
ted. The activation design absolutely must be conservative.<br><br></div><d=
iv>I expect this rigorous standard for soft fork activation will get a BIP =
number. If you are going to propose a future soft fork I recommend you plan=
 for activation in approximately 13 years from the point the soft fork code=
 is merged into Core.<br><br></div><div>I am happy to settle the soft fork =
activation question once and for all for the community. I expect in time my=
 contribution will be recognized in the annals of history with Satoshi Naka=
moto and Hal Finney. <br><br></div><div>Addendum: Although all future soft =
forks will ultimately use this standard, this standard is copyrighted. Ever=
y time it is used royalties must be paid into this quantum secure Bitcoin v=
anity address 1quantumsecureaddress<br><br><br>-- <br>Michael Folkson<br>Em=
ail: <a href=3D"mailto:michaelfolkson@gmail.com" target=3D"_blank">michaelf=
olkson@gmail.com</a><br>Keybase: michaelfolkson<br>PGP: 43ED C999 9F85 1D40=
 EAF4 9835 92D6 0159 214C FEE3</div></div>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div>

--00000000000026ef7a05beed1599--