summaryrefslogtreecommitdiff
path: root/94/99933784e04ae66e5c3c064ea946a5ea46df80
blob: e4a2f4b9a2f37481eee9c63af3d1c5217fad841e (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
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
Return-Path: <marek@palatinus.cz>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 5BFC2267
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 11 May 2016 13:09:29 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-yw0-f174.google.com (mail-yw0-f174.google.com
	[209.85.161.174])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 571F31B8
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 11 May 2016 13:09:27 +0000 (UTC)
Received: by mail-yw0-f174.google.com with SMTP id g133so41668073ywb.2
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 11 May 2016 06:09:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=palatinus-cz.20150623.gappssmtp.com; s=20150623;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc; bh=b6ELHjDNjAsdGOmpBrLPVgEhRor2YrN6lWVr3Cw/eRU=;
	b=pyKUefy3/uG3do/LX3pwwEWjEQPfRKXPzZIOt/UCYs/0FnYSF0QbepKnFV1bvpeFGo
	t3P+lZ61tMMZb25b9JByLS/kPFMqTCEIaNEB7mzBQvhyb91fHXWLLUjT8z9S//NI3ydn
	YwDJeceGExHnCquH/WvucWu1+0BGdLNBUh9XtMt+Lz/xIy07exNQp9rc9R8MQaUKoijN
	ZDdLvyFCrFjbiaI9HV9YEzjqn6NlMy2aQdzgiRKO3edQm8z0kUooVjSaDBKI3a4gfa17
	Rc8FD2o7KULeBZrNwaWFD+egnh2UMzcViyqL02AmR9wCGTikSx75luouDsmWSJhEOqUg
	c3OQ==
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=b6ELHjDNjAsdGOmpBrLPVgEhRor2YrN6lWVr3Cw/eRU=;
	b=by2R+I4a9MY0pdNEJLICpYlQs4zRUZ+iV1Lm2w27R9tBiNAAxAN0jxv6bWV1ZS0jzn
	oYRWzd8C3KyiwQ3BUHJdnKaZQHqG8Fx4pz92h4G+2Qcc4tO7d9X1LFK1VAymjeLx0BES
	pDB9fJtvArXm9CWT2EFaCEsTznuPo0d9OeTyb8C5jcip2Sl8O5gYGzYEjnWNTJbAK0zY
	pO/jefoVAVDiNqhiopzLHB9aM4MSvA7P9mxfXVyuCRs4AoT4zLAzKJiQNTcBVoNb7qCV
	mlDjDcThLSDtZ2ytSlcjhshYdYz9kdB6I5TPbl5zXl93Ts43mjoLqxRQJylKKh3vCBvm
	BkQA==
X-Gm-Message-State: AOPr4FXd/hecI/ca2P8968uZC66b/pTdLBzIgUwRoh07/1E03jlVtUdBfutyt11L3zJCMpQay1qBtP0BNrZpVA==
X-Received: by 10.13.233.68 with SMTP id s65mr1467288ywe.96.1462972166535;
	Wed, 11 May 2016 06:09:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.13.241.2 with HTTP; Wed, 11 May 2016 06:08:57 -0700 (PDT)
In-Reply-To: <CAKzdR-pFZGsQZPrHRbJhviFemSLPf8Bo6UWSaaQ-BurCsnAAWw@mail.gmail.com>
References: <20160510185728.GA1149@fedora-21-dvm>
	<CAE-z3OWvLqONwaN+608jBn9=q1yUvU4ggGrMpA8rE6qmjDQHtg@mail.gmail.com>
	<CAKzdR-ou2FYjjxmRBLARhvfhHO-46weiMc2Q2f+GZf1E_JUEAg@mail.gmail.com>
	<CAKzdR-pFZGsQZPrHRbJhviFemSLPf8Bo6UWSaaQ-BurCsnAAWw@mail.gmail.com>
From: Marek Palatinus <marek@palatinus.cz>
Date: Wed, 11 May 2016 15:08:57 +0200
Message-ID: <CAJna-HjM-4D4EXMkeSSquRT3r0TMWd+zL8ZRZZ5iQfesqZdB2g@mail.gmail.com>
To: Sergio Demian Lerner <sergio.d.lerner@gmail.com>, 
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=94eb2c060c164dc27c053290c06d
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, 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] Making AsicBoost irrelevant
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: Wed, 11 May 2016 13:09:29 -0000

--94eb2c060c164dc27c053290c06d
Content-Type: text/plain; charset=UTF-8

Ehm, I though those discussions about "ASICs are bad, because X" ended
years ago by starting "ASIC unfriendly" altcoins. ASIC industry is twisted
even without AsicBoost. I don't see any particular reason why to change
rules just because of 10% edge.

This is opening Pandora box and it is potentially extremely dangerous for
the health of the network. You cannot know in advance what you'll break by
changing the rules.

Disclaimer: I don't have any stake in any ASIC company/facility.

slush

On Wed, May 11, 2016 at 2:20 PM, Sergio Demian Lerner via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

>
>
> On Tue, May 10, 2016 at 6:43 PM, Sergio Demian Lerner <
> sergio.d.lerner@gmail.com> wrote:
>
>>
>>
>> You can find it here:
>> https://bitslog.wordpress.com/2014/03/18/the-re-design-of-the-bitcoin-block-header/
>>
>> Basically, the idea is to put in the first 64 bytes a 4 byte hash of the
>> second 64-byte chunk. That design also allows increased nonce space in the
>> first 64 bytes.
>>
>> My mistake here. I didn't recalled correctly my own idea. The idea is to
> include in the second 64-byte chunk a 4-byte hash of the first chunk, not
> the opposite.
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>

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

<div dir=3D"ltr">Ehm, I though those discussions about &quot;ASICs are bad,=
 because X&quot; ended years ago by starting &quot;ASIC unfriendly&quot; al=
tcoins.=C2=A0ASIC industry is twisted even without AsicBoost. I don&#39;t s=
ee any particular reason why to change rules just because of 10%=C2=A0edge.=
<div><br></div><div>This is opening Pandora box and it is potentially extre=
mely dangerous for the health of the network. You cannot know in advance wh=
at you&#39;ll break by changing the rules.</div><div><br></div><div>Disclai=
mer: I don&#39;t have any stake in any ASIC company/facility.</div><div><br=
></div><div>slush</div></div><div class=3D"gmail_extra"><br><div class=3D"g=
mail_quote">On Wed, May 11, 2016 at 2:20 PM, Sergio Demian Lerner via bitco=
in-dev <span dir=3D"ltr">&lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfound=
ation.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</a>&gt;<=
/span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><br><div c=
lass=3D"gmail_extra"><br><div class=3D"gmail_quote"><span class=3D"">On Tue=
, May 10, 2016 at 6:43 PM, Sergio Demian Lerner <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:sergio.d.lerner@gmail.com" target=3D"_blank">sergio.d.lerner@g=
mail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=
=3D"ltr"><div><div><div><div><br><div><br></div>You can find it here: <a hr=
ef=3D"https://bitslog.wordpress.com/2014/03/18/the-re-design-of-the-bitcoin=
-block-header/" target=3D"_blank">https://bitslog.wordpress.com/2014/03/18/=
the-re-design-of-the-bitcoin-block-header/</a><br></div><div><br></div>Basi=
cally, the idea is to put in the first 64 bytes a 4 byte hash of the second=
 64-byte chunk. That design also allows increased nonce space in the first =
64 bytes. <br><br></div></div></div></div></blockquote></span><div>My mista=
ke here. I didn&#39;t recalled correctly my own idea. The idea is to includ=
e in the second 64-byte chunk a 4-byte hash of the first chunk, not the opp=
osite. <br><div><br></div></div></div></div></div>
<br>_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
<br></blockquote></div><br></div>

--94eb2c060c164dc27c053290c06d--