FYI, it is now safe consensus-wise at this point to build the server
stack as follows:

--with-consensus --with-secp256k1 --without-openssl

I will change the build so that this is the default. With recent changes
to secp256k1 initialization there is negligible performance impact to
building in this configuration as opposed to native libbitcoin script
checks (--without-consensus).

e


-------- Forwarded Message --------
Subject: Re: [bitcoin-dev] Libconsensus separated repository (was
Bitcoin Core and hard forks)
Date: Tue, 28 Jul 2015 10:47:19 +0200
From: Wladimir J. van der Laan <laanwj@???>
To: Eric Voskuil <eric@???>
CC: Jorge Timón <jtimon@???>, bitcoin-dev@???

On Mon, Jul 27, 2015 at 11:40:42PM -0700, Eric Voskuil via bitcoin-dev
wrote:

> It's a performance sacrifice, and then there's the OpenSSL dependency,
> but these are both optional within our stack - so the application
> developer has the option. So the only downside is that we are
> maintaining the conditional compilation.

Now that BIP66 became active, and only strict DER signatures are
allowed, the OpenSSL dependency can be removed from consensus.

Pieter Wuille will do an announcement on this soon.

Wladimir