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
|
Return-Path: <pete@petertodd.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 1650971E
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 10 May 2016 19:13:08 +0000 (UTC)
X-Greylist: delayed 00:15:34 by SQLgrey-1.7.6
Received: from outmail148107.authsmtp.com (outmail148107.authsmtp.com
[62.13.148.107])
by smtp1.linuxfoundation.org (Postfix) with ESMTP id 4E2D71C5
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 10 May 2016 19:13:06 +0000 (UTC)
Received: from mail-c232.authsmtp.com (mail-c232.authsmtp.com [62.13.128.232])
by punt22.authsmtp.com (8.14.2/8.14.2/) with ESMTP id u4AIvV9u057206
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 10 May 2016 19:57:31 +0100 (BST)
Received: from petertodd.org (ec2-52-5-185-120.compute-1.amazonaws.com
[52.5.185.120]) (authenticated bits=0)
by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id u4AIvTsk027690
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 10 May 2016 19:57:30 +0100 (BST)
Received: from [127.0.0.1] (localhost [127.0.0.1])
by petertodd.org (Postfix) with ESMTPSA id 24D2D400F7
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 10 May 2016 18:56:11 +0000 (UTC)
Received: by localhost (Postfix, from userid 1000)
id BAD69205A7; Tue, 10 May 2016 14:57:28 -0400 (EDT)
Date: Tue, 10 May 2016 14:57:28 -0400
From: Peter Todd <pete@petertodd.org>
To: bitcoin-dev@lists.linuxfoundation.org
Message-ID: <20160510185728.GA1149@fedora-21-dvm>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature"; boundary="1yeeQ81UyVL57Vl7"
Content-Disposition: inline
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Server-Quench: 0c16513b-16e1-11e6-829e-00151795d556
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVJwpGK10IU0Fd
P1hyKltILEZaQVBf Ri5dBBEKBAw1ADwr dVUTOktcYlUzDkx1
UkhIREJTHQ9tBhYC BlAbUAd3aQROfWBx Z0Z9XHVEXQo/cTcE
BCoXTm0EYmFpaC4d UEVeOQMHcQVPfxwX d1F5AXIQYGRSYGdo
RV4+emhpZGgGd3UI TlxQc0Q3SEUKGDF0 bgsDFh8oGlYZDyQp NREiJ0AVGlp5
X-Authentic-SMTP: 61633532353630.1037:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 52.5.185.120/25
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
anti-virus system.
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW
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: Tue, 10 May 2016 19:31:15 +0000
Subject: [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: Tue, 10 May 2016 19:13:08 -0000
--1yeeQ81UyVL57Vl7
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
As part of the hard-fork proposed in the HK agreement(1) we'd like to make =
the
patented AsicBoost optimisation useless, and hopefully make further similar
optimizations useless as well.
What's the best way to do this? Ideally this would be SPV compatible, but i=
f it
requires changes from SPV clients that's ok too. Also the fix this should be
compatible with existing mining hardware.
1) https://medium.com/@bitcoinroundtable/bitcoin-roundtable-consensus-266d4=
75a61ff
2) http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-April/012596=
=2Ehtml
--=20
https://petertodd.org 'peter'[:-1]@petertodd.org
--1yeeQ81UyVL57Vl7
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
iQEcBAEBCAAGBQJXMi8VAAoJEGOZARBE6K+y018H/jaa8jP75eOLQNlkOvLI3s4U
ilwIXGxKEVgfNIxyTJRuo/Nmi8thPLohD2w7LxN77diJMUhdMoHF279q3zUYbZDn
T2M4uv4Ht2gznqFY1pbTufXzwXqxxS4VkKjXnbA6YARRXvDeOiXz71K9FhhBMgWV
AGglOig++CfXR6nh7llz55aKfOgmXRuvIjRT9L36SGd+hSbE4gNJIFqjRcaEwk+h
srI0SqgBi5cAIV8JOLIWKVL8bWxVVU4YfeYSnbCFhdwUCRpzQ/43k9jTvKR1Fy8i
CO5tH99cKoOKkFHvFG9UMoJQAjdcsV3ZrBHFJvkYtyspfWywPqwMnS017W9TASM=
=AsJv
-----END PGP SIGNATURE-----
--1yeeQ81UyVL57Vl7--
|
