MIME-Version: 1.0
In-Reply-To: <CANN4kmdMcbQ9pYC44a02+wzzVzoMt8n5TAL=Z3bRaBkT_6Vnpg@mail.gmail.com>
References: <BL2PR03MB435F510935FC7E230118AD3EE380@BL2PR03MB435.namprd03.prod.outlook.com>
	<CAAy62_K5ePDuvVn8=DtwJX6ek00Z_r4u9LyA0W11vgZmQ=zzDg@mail.gmail.com>
	<CANN4kmdMcbQ9pYC44a02+wzzVzoMt8n5TAL=Z3bRaBkT_6Vnpg@mail.gmail.com>
From: David Vorick <david.vorick@gmail.com>
Date: Mon, 20 Mar 2017 14:51:51 -0400
Message-ID: <CAFVRnyrsH_Oh2XXzRf9P5shysw4ah6AGmHhNyJ582AAhnDcaTw@mail.gmail.com>
To: Nick ODell <nickodell@gmail.com>, 
	Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a114695fc49b561054b2e0550
Subject: Re: [bitcoin-dev] Malice Reactive Proof of Work Additions (MR
 POWA): Protecting Bitcoin from malicious miners
Precedence: list

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

I am in support of having multiple PoW forks to choose from, but it is
indeed problematic to have one chain running a rotation of algorithms.

The reason I support multiple algos is because we don't want an attacker
secretly making asics ahead of time in the event of an emergency PoW fork.
We want them to be uncertain which of a large selection of algorithms are
going to be used, making pre-emptive asic manufacturing more difficult.

But once an algorithm is chosen that should be the end of the story, just
one algo without rotation.

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

<div dir=3D"auto"><div><div class=3D"gmail_extra">I am in support of having=
 multiple PoW forks to choose from, but it is indeed problematic to have on=
e chain running a rotation of algorithms.</div></div><div class=3D"gmail_ex=
tra" dir=3D"auto"><br></div><div class=3D"gmail_extra" dir=3D"auto">The rea=
son I support multiple algos is because we don&#39;t want an attacker secre=
tly making asics ahead of time in the event of an emergency PoW fork. We wa=
nt them to be uncertain which of a large selection of algorithms are going =
to be used, making pre-emptive asic manufacturing more difficult.</div><div=
 class=3D"gmail_extra" dir=3D"auto"><br></div><div class=3D"gmail_extra" di=
r=3D"auto">But once an algorithm is chosen that should be the end of the st=
ory, just one algo without rotation.</div></div>

--001a114695fc49b561054b2e0550--