From: "Jeremy Spilman" <jeremy@taplink•co>
To: "Bitcoin Dev" <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] 0.8.5 with libsecp256k1
Date: Wed, 09 Oct 2013 21:10:09 -0700 [thread overview]
Message-ID: <op.w4p0i7a3yldrnw@laptop-air> (raw)
In-Reply-To: <CAEz79PrCSjSV=FcSMyYtNip8Jg8oa8nMaHbqKNKKyoB-NEqRDQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1390 bytes --]
Can this be combined with the ideas on deterministic signing to show
matching signatures with OpenSSL's implementation?
Not sure if that's worth much, since we would just be testing needles in a
very large haystack, but better than nothing?
On Wed, 09 Oct 2013 20:50:30 -0700, 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
[-- Attachment #2.1: Type: text/html, Size: 2048 bytes --]
next prev parent reply other threads:[~2013-10-10 5:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-10 3:50 Warren Togami Jr.
2013-10-10 4:10 ` Jeremy Spilman [this message]
2013-10-10 14:21 ` [Bitcoin-development] malleability work-around vs fix (Re: 0.8.5 with libsecp256k1) Adam Back
2013-10-10 15:06 ` Adam Back
2013-10-10 8:29 ` [Bitcoin-development] 0.8.5 with libsecp256k1 Mike Hearn
2013-10-11 11:41 ` Pieter Wuille
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=op.w4p0i7a3yldrnw@laptop-air \
--to=jeremy@taplink$(echo .)co \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox