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
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1VUBcd-0005RK-AI
for bitcoin-development@lists.sourceforge.net;
Thu, 10 Oct 2013 08:29:27 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.46 as permitted sender)
client-ip=209.85.219.46; envelope-from=mh.in.england@gmail.com;
helo=mail-oa0-f46.google.com;
Received: from mail-oa0-f46.google.com ([209.85.219.46])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VUBcc-0002AP-DL
for bitcoin-development@lists.sourceforge.net;
Thu, 10 Oct 2013 08:29:27 +0000
Received: by mail-oa0-f46.google.com with SMTP id k14so1166167oag.5
for <bitcoin-development@lists.sourceforge.net>;
Thu, 10 Oct 2013 01:29:21 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.182.200.129 with SMTP id js1mr316943obc.55.1381393761008;
Thu, 10 Oct 2013 01:29:21 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.156.42 with HTTP; Thu, 10 Oct 2013 01:29:20 -0700 (PDT)
In-Reply-To: <CAEz79PrCSjSV=FcSMyYtNip8Jg8oa8nMaHbqKNKKyoB-NEqRDQ@mail.gmail.com>
References: <CAEz79PrCSjSV=FcSMyYtNip8Jg8oa8nMaHbqKNKKyoB-NEqRDQ@mail.gmail.com>
Date: Thu, 10 Oct 2013 10:29:20 +0200
X-Google-Sender-Auth: TeM3f1f8eScHkZoRhlcs725Df8A
Message-ID: <CANEZrP16LEwJLAFniFgNDODohP37bT0fmrQbR+FQEmwDThh-0g@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: "Warren Togami Jr." <wtogami@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c236966b817304e85ecc57
X-Spam-Score: -0.5 (/)
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: doubleclick.net]
-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
(mh.in.england[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_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: 1VUBcc-0002AP-DL
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [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 08:29:27 -0000
--001a11c236966b817304e85ecc57
Content-Type: text/plain; charset=UTF-8
Thanks! I'd love to see this library become usable behind a command line
flag or config setting. At some point we're going to want to switch to it.
I believe the main issue at the moment is the malleability issues? If so,
it would seem possible to use OpenSSL to parse the signature into
components and then libsecp256k1 to verify them.
On Thu, Oct 10, 2013 at 5:50 AM, Warren Togami Jr. <wtogami@gmail.com>wrote:
> 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
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
> from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
--001a11c236966b817304e85ecc57
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Thanks! I'd love to see this library become usable beh=
ind a command line flag or config setting. At some point we're going to=
want to switch to it.<div><br></div><div>I believe the main issue at the m=
oment is the malleability issues? If so, it would seem possible to use Open=
SSL to parse the signature into components and then libsecp256k1 to verify =
them.</div>
<div><br></div><div><br></div></div><div class=3D"gmail_extra"><br><br><div=
class=3D"gmail_quote">On Thu, Oct 10, 2013 at 5:50 AM, Warren Togami Jr. <=
span dir=3D"ltr"><<a href=3D"mailto:wtogami@gmail.com" target=3D"_blank"=
>wtogami@gmail.com</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><div><a href=3D"https:=
//github.com/sipa/secp256k1" target=3D"_blank">https://github.com/sipa/secp=
256k1</a><br>
</div><div>sipa's secp256k1, optimized 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" target=3D"_blank">https://github.com/wtogami/bitcoin/commits=
/btc-0.8.5-secp256k1</a><div>This branch should theoretically work for Linu=
x, win32 gitian and mac builds. =C2=A0These commits are rather ugly because=
it was thrown together just to make it build with the old 0.8 makefiles wi=
thout intent for production code merge. cfields is working on autotoolizing=
it as one of the prerequisites prior to inclusion into bitcoin master wher=
e it will be an option disabled by default.<br>
<div><br></div><div><a href=3D"http://193.28.235.60/~warren/bitcoin-0.8.5-s=
ecp256k1/" target=3D"_blank">http://193.28.235.60/~warren/bitcoin-0.8.5-sec=
p256k1/</a><br></div><div>Untested win32 gitian build. =C2=A0Build your own=
Linux or Mac builds if you want to test it. =C2=A0Not recommended for prod=
uction wallet or mining uses.</div>
<span class=3D"HOEnZb"><font color=3D"#888888">
</font></span></div><span class=3D"HOEnZb"><font color=3D"#888888"><div><br=
></div><div>Warren</div></font></span></div>
<br>-----------------------------------------------------------------------=
-------<br>
October Webinars: Code for Performance<br>
Free Intel webinars can help you accelerate application performance.<br>
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most fr=
om<br>
the latest Intel processors and coprocessors. See abstracts and register &g=
t;<br>
<a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D60134071&iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D60134071&iu=3D/4140/ostg.clktrk</a><br>___________________=
____________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
<br></blockquote></div><br></div>
--001a11c236966b817304e85ecc57--
|
