On Sun, Jan 17, 2016 at 11:57:28PM +0100, xor--- via bitcoin-dev wrote:
> On Sunday, January 17, 2016 11:08:08 AM Wladimir J. van der Laan via bitcoin-
> dev wrote:
> > Preliminary release notes for the release can be found here:
> >
> >
TLDR:
1.7MB effective block size is a better estimate than 1.6MB for p2pkh
with segwit. 2MB for 2/2 multisig still seems accurate.
Additional post-segwit soft forked script improvements can improve
the effective block size for p2pkh txns from 1.7MB to 1.9MB, and for
2/2 multisig from
On Saturday, September 05, 2015 9:19:51 PM Andy Chase wrote:
> Okay for sure yeah writing another proposal that reflects the current state
> of affairs as people see it might provide some interesting perspective on
> this proposal. I would welcome that.
Are you saying your proposal is
In the release notes for 0.12, it says that we have moved from using
OpenSSL to libsecp256k1 for signature validation. So what else is it being
used for that we need to keep it as a dependency?
Thanks,
Andrew
___
bitcoin-dev mailing list
I believe libsecp256k1 just performs Elliptic Curve operations
required by Bitcoin. OpenSSL is used for all other crypto.
For instance the PRNG appears to be OpenSSL:
https://github.com/bitcoin/bitcoin/blob/master/src/random.h
On Mon, Jan 18, 2016 at 8:39 PM, Andrew C via bitcoin-dev