[Bitcoin-development] Fwd: [Bug 24444] Named Curve Registry (adding secp256k1)

2014-10-13 Thread Melvin Carvalho
FYI: This is an issue I filed related to adding secp256k1 into Web Crypto API which will be implemented natively in (some) web browsers. If there is any feedback from crypto implementers, please feel free to add comments to this thread: https://www.w3.org/Bugs/Public/show_bug.cgi?id=2

[Bitcoin-development] OpenCryptocurrencyReview

2014-10-13 Thread Daniel Murrell
Dear All I'm not sure this is welcome here. Someone suggested I let the devs know about it here. I've made an open forum on which to post discussion about cryptocurrency related research: www.opencryptocurrencyreview.com Jeff helped me with the naming a bit some time ago. It's not had much

Re: [Bitcoin-development] Fwd: [Bug 24444] Named Curve Registry (adding secp256k1)

2014-10-13 Thread Matt Corallo
See-also: this related bug on Curve25519 and some MS Research curves that generated far more discussion. https://www.w3.org/Bugs/Public/show_bug.cgi?id=25839 Matt On 10/13/14 10:01, Melvin Carvalho wrote: FYI: This is an issue I filed related to adding secp256k1 into Web Crypto API which

Re: [Bitcoin-development] Request for review/testing: headers-first synchronization in Bitcoin Core

2014-10-13 Thread 21E14
When forgoing bootstrapping due to disk space constraints, you, and the network, are likely better off -reindex-ing from current blk000??.dat files. Which brings up an interesting point: The improvements related to the headers first approach are likely to increase, how ever marginally, the

[Bitcoin-development] Malleable booleans

2014-10-13 Thread Pieter Wuille
Hi all, while working on a BIP62 implementation I discovered yet another type of malleability: the interpretation of booleans. Any byte array with non-zero bytes in it (ignoring the highest bit of the last byte, which is the sign bit when interpreting as a number) is interpreted as true,

Re: [Bitcoin-development] Malleable booleans

2014-10-13 Thread Gregory Maxwell
On Tue, Oct 14, 2014 at 2:34 AM, Pieter Wuille pieter.wui...@gmail.com wrote: Hi all, while working on a BIP62 implementation I discovered yet another type of malleability: the interpretation of booleans. Any byte array with non-zero bytes in it (ignoring the highest bit of the last byte,