-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
secp224r1 not working with pointFromX #21
Comments
How about we just remove |
I think that would be a responsible decision, but maybe also a note in the |
Found a source for the optimization: http://eprint.iacr.org/2012/309.pdf. |
Ok, this is simply because the prime chosen in
This is mentioned as a pre-condition in the paper referenced above. I don't see any easy way of getting around this in |
OK, I'd be in favor of getting rid of the curve. I doubt many will use it Thoughts? On Mon, Jun 23, 2014 at 10:52 PM, Daniel Cousens [email protected]
Simple & Secure Bitcoin Wallet: https://www.coinbolt.com |
Now that we're aware of the underlying issue, I'm perfectly OK with removing the curve and just making a note, at least until a better solution is found. |
Removed the curve in 1.0.0. |
As can be seen in the tests we currently skip
secp224r1
in the tests because it is not fully supported.This appears to be because we are using a curve specific optimization in
curve.js
: https://github.com/cryptocoinjs/ecurve/blob/master/lib/curve.js#L22.Porting over to
bn.js
does resolve this issue, but because we aren't using the reduction contexts all the way through, it has a huge performance hit.For now, it seems better to just flag this as obvious as possible and keep building up tests around the library.
The text was updated successfully, but these errors were encountered: