1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
|
Return-Path: <david.vorick@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id EF58BB35
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 20 Mar 2017 18:51:54 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wm0-f50.google.com (mail-wm0-f50.google.com [74.125.82.50])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 5E80D123
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 20 Mar 2017 18:51:54 +0000 (UTC)
Received: by mail-wm0-f50.google.com with SMTP id t189so72200204wmt.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 20 Mar 2017 11:51:54 -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=4DLWnCv48kMctvDZ1kfjtIj86sGkpPicxc7RBBo+4d4=;
b=naVItSAePn5AFgEoE24YeeU3uQ60M2KJd1stZ3cAwEGbLE97kXnbZwm+a56V7CQzPE
XSpBs715Ubc+FSQJ1b5RQWssm9yqMyc6W6mMRZiDdgSFYiFfhQ8EFCL4CFUZDTKEX2KZ
2sdfIjX6zMFIGKgGA971D/eOiqdfCIoRD3cdwWFpVN/fVGblzRIQRvy7dMth103Vbptd
DSwjFw7jbpgXaS1ZkBQe/iTXkMHkj9O8JZ9GbpfJIcXJfHkIYbrGKaBhr8LGM/8yCFUp
dPxzYP8kYTccFwZ4KAlpWpRmIaa0UwSA9uVmiE0eWWtvmTlgmRECahcGWVtTY5zNIlNg
JSnQ==
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=4DLWnCv48kMctvDZ1kfjtIj86sGkpPicxc7RBBo+4d4=;
b=K8pXIucIEb0zKAa0xVmZThGixc52acw/dM8FHm3J18wy2ZRf3zr8R8AJenAwoQV/U1
La7vW+aGkJM5YYBaqiAW24pHWALH01OxY6G77DH9w8VQvsAlxDPlL5sTIlTO/uUd60ah
gu8rOCxkuLBxKWe3QTeq5+3HuguwLz4AaqNt36Js4eU2KUBvkcEeov/mjimy3YvujFBe
Mb6N4+rOqqZNBfCxZt/66JYdIN5/v6EUdqS320fXaLlCjItlEbdawtZrY+cphMN/oerP
vRC7Fo5m25hOuClTOSCphgk5zpBBusPWeHF0/9TKQb3rdJBswIBv1rH6pbxUlDNrpoyN
KndQ==
X-Gm-Message-State: AFeK/H2tsGYTaxg8XusMoCU2PxIZHbcPbNmy1Bl96fhdb8eaxgWzqyrlEb3bclvVsC41d5nzKZv3hEPNj89kOA==
X-Received: by 10.28.217.136 with SMTP id q130mr11232950wmg.132.1490035912847;
Mon, 20 Mar 2017 11:51:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.55.9 with HTTP; Mon, 20 Mar 2017 11:51:51 -0700 (PDT)
Received: by 10.28.55.9 with HTTP; Mon, 20 Mar 2017 11:51:51 -0700 (PDT)
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
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
Subject: Re: [bitcoin-dev] Malice Reactive Proof of Work Additions (MR
POWA): Protecting Bitcoin from malicious miners
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: Mon, 20 Mar 2017 18:51:55 -0000
--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'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--
|
