Date: Sat, 2 Oct 2021 11:19:37 +0200 (CEST)
From: Prayank <prayank@tutanota.de>
To: Ryan Grant <bitcoin-dev@rgrant.org>
Message-ID: <Ml-IIuL--3-2@tutanota.de>
In-Reply-To: <CAMnpzfrNZ0vpiMVoH=0KW9jy1-vppudX3D7Z+aXpSp4h_7s=zw@mail.gmail.com>
References: <MkZx3Hv--3-2@tutanota.de>
 <yp9mJ2Poc_Ce91RkrhjnTA3UPvdh0wUyw2QhRPZEyO3gPHZPhmnhqER_4b7ChvmRh8GcYVPEkoud6vamJ9lGlQPi-POF-kyimBWNHz2RH3A=@protonmail.com>
 <MkdYcV9--3-2@tutanota.de>
 <CAPv7TjbvRE-b33MeYucUfr6CTooCRSH42hwSn5dMiJ4LODATRQ@mail.gmail.com>
 <MktnWM7--3-2@tutanota.de>
 <qNjz-H23x07OJjnf5Try4Qp8l5s23SQxhEE8yAfNbrniN34u2vM72FVFSDJxHg4HNTL8tdcm-KKT8h6XVRwOwN0ZmckxzWiMlNFmLbMNuHc=@protonmail.com>
 <MkwZGYl--7-2@tutanota.de>
 <CAMnpzfrNZ0vpiMVoH=0KW9jy1-vppudX3D7Z+aXpSp4h_7s=zw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
 boundary="----=_Part_847733_668536719.1633166377777"
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Mock introducing vulnerability in important
 Bitcoin projects
Precedence: list

------=_Part_847733_668536719.1633166377777
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

This looks interesting although I don't understand few things:

> The scheme should include public precommitments collected at ceremonial intervals.

How would this work? Can you explain with an example please.

> Upon assignment, the dev would have community approval to opportunistically insert a security flaw

Who is doing the assignment?

-- 
Prayank

A3B1 E430 2298 178F


Oct 2, 2021, 01:45 by bitcoin-dev@rgrant.org:

> Due to the uneven reputation factor of various devs, and uneven review
> attention for new pull requests, this exercise would work best as a
> secret sortition.
>
> Sortition would encourage everyone to always be on their toes rather
> than only when dealing with new github accounts or declared Red Team
> devs.  The ceremonial aspects would encourage more devs to participate
> without harming their reputation.
>
>  https://en.wikipedia.org/wiki/Sortition
>  https://en.wikipedia.org/wiki/Red_team
>
> The scheme should include public precommitments collected at
> ceremonial intervals.
>
> where:
>  hash1 /* sortition ticket */     = double-sha256(secret)
>  hash2 /* public precommitment */ = double-sha256(hash1)
>
> The random oracle could be block hashes.  They could be matched to
> hash1, the sortition ticket.  A red-team-concurrency difficulty
> parameter could control how many least-significant bits must match to
> be secretly selected.  The difficulty parameter could be a matter of
> group consensus at the ceremonial intervals, based on a group decision
> on how much positive effect the Red Team exercise is providing.
>
> Upon assignment, the dev would have community approval to
> opportunistically insert a security flaw; which, when either caught,
> merged, or on timeout, they would reveal along with the sortition
> ticket that hashes to their public precommitment.
>
> Sortition Precommitment Day might be once or twice a year.
>


------=_Part_847733_668536719.1633166377777
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DUTF-8=
">
  </head>
  <body>
<div>This looks interesting although I don't understand few things:<br></di=
v><div dir=3D"auto"><br></div><div dir=3D"auto">&gt; The scheme should incl=
ude public precommitments collected at ceremonial intervals.<br></div><div =
dir=3D"auto"><br></div><div dir=3D"auto">How would this work? Can you expla=
in with an example please.<br></div><div dir=3D"auto"><br></div><div dir=3D=
"auto">&gt; Upon assignment, the dev would have community approval to oppor=
tunistically insert a security flaw<br></div><div dir=3D"auto"><br></div><d=
iv dir=3D"auto">Who is doing the assignment?<br></div><div><br></div><div>-=
- <br></div><div>Prayank<br></div><div><br></div><div dir=3D"auto">A3B1 E43=
0 2298 178F<br></div><div><br></div><div><br></div><div><br></div><div>Oct =
2, 2021, 01:45 by bitcoin-dev@rgrant.org:<br></div><blockquote class=3D"tut=
anota_quote" style=3D"border-left: 1px solid #93A3B8; padding-left: 10px; m=
argin-left: 5px;"><div>Due to the uneven reputation factor of various devs,=
 and uneven review<br></div><div>attention for new pull requests, this exer=
cise would work best as a<br></div><div>secret sortition.<br></div><div><br=
></div><div>Sortition would encourage everyone to always be on their toes r=
ather<br></div><div>than only when dealing with new github accounts or decl=
ared Red Team<br></div><div>devs.  The ceremonial aspects would encourage m=
ore devs to participate<br></div><div>without harming their reputation.<br>=
</div><div><br></div><div> https://en.wikipedia.org/wiki/Sortition<br></div=
><div> https://en.wikipedia.org/wiki/Red_team<br></div><div><br></div><div>=
The scheme should include public precommitments collected at<br></div><div>=
ceremonial intervals.<br></div><div><br></div><div>where:<br></div><div> ha=
sh1 /* sortition ticket */     =3D double-sha256(secret)<br></div><div> has=
h2 /* public precommitment */ =3D double-sha256(hash1)<br></div><div><br></=
div><div>The random oracle could be block hashes.  They could be matched to=
<br></div><div>hash1, the sortition ticket.  A red-team-concurrency difficu=
lty<br></div><div>parameter could control how many least-significant bits m=
ust match to<br></div><div>be secretly selected.  The difficulty parameter =
could be a matter of<br></div><div>group consensus at the ceremonial interv=
als, based on a group decision<br></div><div>on how much positive effect th=
e Red Team exercise is providing.<br></div><div><br></div><div>Upon assignm=
ent, the dev would have community approval to<br></div><div>opportunistical=
ly insert a security flaw; which, when either caught,<br></div><div>merged,=
 or on timeout, they would reveal along with the sortition<br></div><div>ti=
cket that hashes to their public precommitment.<br></div><div><br></div><di=
v>Sortition Precommitment Day might be once or twice a year.<br></div></blo=
ckquote><div dir=3D"auto"><br></div>  </body>
</html>

------=_Part_847733_668536719.1633166377777--