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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <wtogami@gmail.com>) id 1VU7Gn-00070o-0n
for bitcoin-development@lists.sourceforge.net;
Thu, 10 Oct 2013 03:50:37 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.160.44 as permitted sender)
client-ip=209.85.160.44; envelope-from=wtogami@gmail.com;
helo=mail-pb0-f44.google.com;
Received: from mail-pb0-f44.google.com ([209.85.160.44])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VU7Gm-0004R0-2c
for bitcoin-development@lists.sourceforge.net;
Thu, 10 Oct 2013 03:50:36 +0000
Received: by mail-pb0-f44.google.com with SMTP id xa7so1910570pbc.31
for <bitcoin-development@lists.sourceforge.net>;
Wed, 09 Oct 2013 20:50:30 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.68.255.229 with SMTP id at5mr11500021pbd.130.1381377030161;
Wed, 09 Oct 2013 20:50:30 -0700 (PDT)
Received: by 10.66.158.129 with HTTP; Wed, 9 Oct 2013 20:50:30 -0700 (PDT)
Date: Wed, 9 Oct 2013 17:50:30 -1000
Message-ID: <CAEz79PrCSjSV=FcSMyYtNip8Jg8oa8nMaHbqKNKKyoB-NEqRDQ@mail.gmail.com>
From: "Warren Togami Jr." <wtogami@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=047d7b5da0db2f248b04e85ae790
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information. [URIs: github.com]
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(wtogami[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.0 NORMAL_HTTP_TO_IP URI: Uses a dotted-decimal IP address in URL
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1VU7Gm-0004R0-2c
Subject: [Bitcoin-development] 0.8.5 with libsecp256k1
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 10 Oct 2013 03:50:37 -0000
--047d7b5da0db2f248b04e85ae790
Content-Type: text/plain; charset=UTF-8
https://github.com/sipa/secp256k1
sipa's secp256k1, optimized ecdsa, significantly faster than openssl
Today someone in #bitcoin-dev asked for Bitcoin 0.8.5 with sipa's
secp256k1. Litecoin has been shipping test builds with secp256k1 for
several months now so it was a simple matter to throw together a branch of
Bitcoin 0.8.5 with secp256k1.
https://github.com/wtogami/bitcoin/commits/btc-0.8.5-secp256k1
This branch should theoretically work for Linux, win32 gitian and mac
builds. These commits are rather ugly because it was thrown together just
to make it build with the old 0.8 makefiles without intent for production
code merge. cfields is working on autotoolizing it as one of the
prerequisites prior to inclusion into bitcoin master where it will be an
option disabled by default.
http://193.28.235.60/~warren/bitcoin-0.8.5-secp256k1/
Untested win32 gitian build. Build your own Linux or Mac builds if you
want to test it. Not recommended for production wallet or mining uses.
Warren
--047d7b5da0db2f248b04e85ae790
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div><div><a href=3D"https://github.com/sipa/secp256k1">ht=
tps://github.com/sipa/secp256k1</a><br></div><div>sipa's secp256k1, opt=
imized ecdsa, significantly faster than openssl</div></div><div><br></div><=
div>
Today someone in #bitcoin-dev asked for Bitcoin 0.8.5 with sipa's secp2=
56k1. =C2=A0Litecoin has been shipping test builds with secp256k1 for sever=
al months now so it was a simple matter to throw together a branch of Bitco=
in 0.8.5 with secp256k1.</div>
<div><br></div><a href=3D"https://github.com/wtogami/bitcoin/commits/btc-0.=
8.5-secp256k1">https://github.com/wtogami/bitcoin/commits/btc-0.8.5-secp256=
k1</a><div>This branch should theoretically work for Linux, win32 gitian an=
d mac builds. =C2=A0These commits are rather ugly because it was thrown tog=
ether just to make it build with the old 0.8 makefiles without intent for p=
roduction code merge. cfields is working on autotoolizing it as one of the =
prerequisites prior to inclusion into bitcoin master where it will be an op=
tion disabled by default.<br>
<div><br></div><div><a href=3D"http://193.28.235.60/~warren/bitcoin-0.8.5-s=
ecp256k1/">http://193.28.235.60/~warren/bitcoin-0.8.5-secp256k1/</a><br></d=
iv><div>Untested win32 gitian build. =C2=A0Build your own Linux or Mac buil=
ds if you want to test it. =C2=A0Not recommended for production wallet or m=
ining uses.</div>
</div><div><br></div><div>Warren</div></div>
--047d7b5da0db2f248b04e85ae790--
|
