summaryrefslogtreecommitdiff
path: root/84/5dc99cc4c2fbcaf346bc2f8e5313c4dfd06801
blob: 22297ee4f10a8db4aa46301dc9c3c63f54c71795 (plain)
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
122
123
Return-Path: <jaejoon@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 552725AC
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat,  8 Apr 2017 22:19:14 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wm0-f44.google.com (mail-wm0-f44.google.com [74.125.82.44])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id C77ED8D
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat,  8 Apr 2017 22:19:13 +0000 (UTC)
Received: by mail-wm0-f44.google.com with SMTP id o81so14517322wmb.1
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 08 Apr 2017 15:19:13 -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=6smhsfqo4VqGsaE0EyTDYYvxjZpxHLAd5Nc8VY0l+TQ=;
	b=DVvdnrzUuA3B5byA14mKNwzTX/QPfhDeL68kaVTL/38dbWYWDRsQh1+iSGv+Dszv8A
	O5ecJoWpyyn2YrlG6TVhRwvU4NcAoljqtpUkpUySXrUPc8ssnezY/ueLitWlTJVebj0H
	JlILlrYxfqHTDLiB3C7svptRYbO8kHE9Ad7abmPcxGSl2hxXt9KY7jNRCTvjqIy9Zb/R
	zUwmnEsb4rjmovqurrd78ImiMP6flaWBush6QV7bsw+ynZDxlYcuMn+AeijyySXz6I+x
	cRNgJeuwEZZpEI3DeFaVrIg1ipEsKcvG8mfTgx4lgnzTqcghGWNyk8Oz6IRbjd08taqw
	Tqxg==
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=6smhsfqo4VqGsaE0EyTDYYvxjZpxHLAd5Nc8VY0l+TQ=;
	b=F0VeEp3Jo16s4+cSCjfmS6PvRIUaop2tovilzt2tPf61coOmxGdiNk0jmB7DO5GUva
	dl+jToBThWPHHR+D+feYSWzIJ/uuzL1h3y/lhWfBsQ8EcsLe8ovUjizIG1yFYRmzMePd
	+ZUgHBhzZYr5qvZPLXrs1+sj6ZwGRB3r4AFN84VA3wAMcZbADLG23sVmWRiPEG9A7QnV
	x8PoJHKsN279r55GddM2efbIYjtVcIz3s+H8Mc9S824c+R69BRUaU8L/5LVqdqtxgXuO
	NjsfDs9ArqzMGuZJaM1Nwx4FlEDGhxQirE5y44v1yKps3MQChsKl0hZ1ltwxBov3fA7w
	Fi/Q==
X-Gm-Message-State: AN3rC/5EghPeX1cevWhVt9XIbDZ0LRCAxN+32s+ggIb1JkV6z+V0nKBE3ShHQLSH7HYKm8MMIlXwV5Pc3T35XA==
X-Received: by 10.28.60.6 with SMTP id j6mr4214530wma.19.1491689952386; Sat,
	08 Apr 2017 15:19:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.134.243 with HTTP; Sat, 8 Apr 2017 15:19:11 -0700 (PDT)
In-Reply-To: <CACDYSUS29qoaNML8XmRz6xDSZsiHe2kYsEFun-kBLaups-OiJg@mail.gmail.com>
References: <CAJR7vkpRhNsQsem-nFkeubX04xx1y7aHwCENfg0d1266oOsXMw@mail.gmail.com>
	<Cwhn7YzwaDUZtOygDAgrU1UXjRPG-EiH3Fyz2c95gqOpNnNbiYL1NvhS28yK5wLJCnIqDaBrM6c574dY-O6_-bRjLIFmDe2NCxIuyV1w2dw=@protonmail.com>
	<CAJR7vkoq8Y_-fbdxN=--gF5wrGByr5oODc4FkTaCEvDSuP0whQ@mail.gmail.com>
	<CACDYSUROutAMV7C8pUXz0PMvH5awkw-XUtce7BxTtZMD_yUm5A@mail.gmail.com>
	<CAJR7vkrn-oFium3wFgcOdqNPuYq+rW2DqyOnkDaCTHabO0y3Xg@mail.gmail.com>
	<CACDYSUS29qoaNML8XmRz6xDSZsiHe2kYsEFun-kBLaups-OiJg@mail.gmail.com>
From: Jimmy Song <jaejoon@gmail.com>
Date: Sat, 8 Apr 2017 17:19:11 -0500
Message-ID: <CAJR7vkp+EXakt3a9+gKU01KpK9qXkuqr3rTrZ8-q6O8rsPhYtg@mail.gmail.com>
To: Pavel Moravec <pavel.moravec@braiins.cz>
Content-Type: multipart/alternative; boundary=001a1148e60aba25b2054caf2192
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
X-Mailman-Approved-At: Sat, 08 Apr 2017 22:20:07 +0000
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] A Small Modification to Segwit
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: Sat, 08 Apr 2017 22:19:14 -0000

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

Pavel,


> I agree. I only wanted to make clear, that the impact would be
> significant. Lot of parties would be involved with nonequivalent
> starting positions.
>
>
I agree with you. I believe nonequivalent starting positions are the norm
in mining, not the exception and hence don't believe this to be a problem.


>
> I think the ASICBoost can and should be prevented completely.
>

It certainly can be and from the responses I'm getting, I believe there
would be at least a few people that would enthusiastically support a BIP to
do that. That is, however, a separate issue than my proposal. My proposal
aims to bring ASICBoost out into the open *while it is still possible*. A
BIP to prevent ASICBoost completely is in that sense compatible.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div=
>Pavel,</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D=
"">
</span>I agree. I only wanted to make clear, that the impact would be<br>
significant. Lot of parties would be involved with nonequivalent<br>
starting positions.<br>
<span class=3D""><br></span></blockquote><div><br></div><div>I agree with y=
ou. I believe nonequivalent starting positions are the norm in mining, not =
the exception and hence don&#39;t believe this to be a problem.</div><div>=
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex"><span class=3D""><br>
</span>I think the ASICBoost can and should be prevented completely.<br></b=
lockquote><div><br></div><div>It certainly can be and from the responses I&=
#39;m getting, I believe there would be at least a few people that would en=
thusiastically support a BIP to do that. That is, however, a separate issue=
 than my proposal. My proposal aims to bring ASICBoost out into the open *w=
hile it is still possible*. A BIP to prevent ASICBoost completely is in tha=
t sense compatible.</div></div></div></div>

--001a1148e60aba25b2054caf2192--