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
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
|
Return-Path: <sergio.d.lerner@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 9B561723
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 2 Oct 2016 22:26:33 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-qk0-f171.google.com (mail-qk0-f171.google.com
[209.85.220.171])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 3947C136
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 2 Oct 2016 22:26:33 +0000 (UTC)
Received: by mail-qk0-f171.google.com with SMTP id o68so8781919qkf.3
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 02 Oct 2016 15:26:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc; bh=1olP7BBJxJhf5X8xP1wgm+HMTwKYNvx0x2ioNx3slko=;
b=TiBe4vQ83hC1JZ1Dgq9mz7YwHnRWBf1Otmoz1QgBGKbKaiOFeB9P2F/w82pfsg4lNw
8wSZz92dk3yq0r4qQ2QKlW2w9DXwCPX96eifYfYV80wdZR3wIGViCtvimJ1AS2ClkNrA
qeWNp44IzD1BeUbc19TSq6ei9ySZam+eGTKbtZZ8o96MUHBVwd5Dh8i8uH9gz4G0TmBx
imM3e9b+jm6Wfjp3T9Njqspo2heQ9i3AldYwg1wlQkfprEfHiFKYxPhrVOfhuEaxXm+8
hAveI/E5pMGDAl59B7y0YpR4O0MgayhkLDelZahU/OOXO470ICV9y+uW9rmJD/FPpEaG
s5+Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc;
bh=1olP7BBJxJhf5X8xP1wgm+HMTwKYNvx0x2ioNx3slko=;
b=mPjyy+3KixKTTIN01MF48L7cAgD9uuCNQwpLd076PdGzBIs86ovcYJrlLqDbUWNs5d
rFAUWWXBMpEo1PwCUCY/uDGPYGTAEUueBMQe+q7IewO8KHmlAbg7/R4h2k01el80zL3E
beQPcQ7EM3HvshINBpJmXcF1Q78TCwwzoV4y7TPn8VNXILcSIK2cbEzcPs1YvA7GAnG1
yq6kkeAM9dsRc2jyF9ZyLn/fw1NOI1X4o/jfkZc/P7r8VysuDvbnAmhXu7MITjYsEfJC
naR+oEuPLVDVZ1L22zcdYil2AW8pNQ/B/JJwLxuPUc8DFLLoYHZO7TBIZebJELJrXgGA
64mw==
X-Gm-Message-State: AA6/9Rmf+iQmEABX0AgYq6dSG+Y07FMHOLM/9cCIlzTi5bX52aNtTu+2a3TvMg4vc5xGD3KltOg2003VYMeycQ==
X-Received: by 10.55.92.71 with SMTP id q68mr18939367qkb.54.1475447192469;
Sun, 02 Oct 2016 15:26:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.237.35.7 with HTTP; Sun, 2 Oct 2016 15:25:52 -0700 (PDT)
In-Reply-To: <CADJgMzuPrvoz5TpO+SvHs_Eix7usFTPuEgxhocjc8tf23LnuOg@mail.gmail.com>
References: <CAKzdR-pAxs_Gim-aFdjd4eQPY6vWsoEVafYwcjmBjit_dsH_wA@mail.gmail.com>
<CADJgMzuPrvoz5TpO+SvHs_Eix7usFTPuEgxhocjc8tf23LnuOg@mail.gmail.com>
From: Sergio Demian Lerner <sergio.d.lerner@gmail.com>
Date: Sun, 2 Oct 2016 19:25:52 -0300
Message-ID: <CAKzdR-p4gs3nz9efYadTehi-KhCh7xRoVXqPN==U9z1PM9SLpw@mail.gmail.com>
To: Btc Drak <btcdrak@gmail.com>
Content-Type: multipart/alternative; boundary=001a114e3e3ecae62a053de95153
X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
RCVD_IN_DNSWL_NONE,
RCVD_IN_SORBS_SPAM autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] About ASICBoost
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: Sun, 02 Oct 2016 22:26:33 -0000
--001a114e3e3ecae62a053de95153
Content-Type: text/plain; charset=UTF-8
It's good you bring that point, and it's very interesting to analyze what
happened then.
We shared our findings with some core developers much earlier than the BIP
proposal. Wether they kept it secret or they shared it with some ASIC
manufacturers is something I don't know. I even mentioned my wishes to try
to give the patent to public domain.
I remember the reason we proposed the BIP is because ASICBoost actually
does NOT require that BIP at all. And that BIP was not a consensus change,
but just a semantic re-interpretation.
ASICBoost can roll the nVersion field or the Merkle root hash. Doing the
former currently generates a strange warning message on nodes and can be
confusing, but doing the later makes ASICBoost completely stealthy. That
BIP could help the community to monitor its use in non-confusing way to the
users. What is worse? I think forcing it to be stealthy is worse.
I never opposed changing Bitcoin to be more decentralized, but hard-forking
a change to the PoW function may be contentious and that path of thought
must be walked very carefully.
Regards
--001a114e3e3ecae62a053de95153
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div><div class=3D"gmail_quote"><div>It's good you bri=
ng that point, and it's very interesting to analyze what happened then.=
<br><br></div>We shared our findings with some core developers much earlier=
than the BIP proposal. Wether they kept it secret or they shared it with s=
ome ASIC manufacturers is something I don't know. I even mentioned my w=
ishes to try to give the patent to public domain.<br>=C2=A0<br>I remember t=
he reason we proposed the BIP is because ASICBoost actually does NOT requir=
e that BIP at all. And that BIP was not a consensus change, but just a sema=
ntic re-interpretation. <br><br>ASICBoost can roll the nVersion field or th=
e Merkle root hash. Doing the former currently generates a strange warning =
message on nodes and can be confusing, but doing the later makes ASICBoost =
completely stealthy. That BIP could help the community to monitor its use i=
n non-confusing way to the users. What is worse? I think forcing it to be s=
tealthy is worse.<br><br>I never opposed changing Bitcoin to be more decent=
ralized, but hard-forking a change to the PoW function may be contentious a=
nd that path of thought must be walked very carefully. <br></div><div class=
=3D"gmail_quote"><br></div><div class=3D"gmail_quote">Regards<br></div></di=
v></div>
--001a114e3e3ecae62a053de95153--
|
