-
Notifications
You must be signed in to change notification settings - Fork 74
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
update secp256k1 to v4.0 #32
Conversation
utACK it looks good to me. |
Bonus: found #33 when verifying this code change. |
Any chance this gets merged and released soon? |
Hi, just wanted to give this a cautious iteration: we have an outstanding release - see ethereumjs/ethereumjs-wallet#113 - and a merge and subsequent release here would substantially improve the installation experience since one main part was to update the If not possible so be it but otherwise a release here would be super cool! 😄 |
@holgerd77 thanks. I had no idea this was used in |
@jprichardson Thanks, that's so great! 😄 |
Published in v2.0.0 🎉 |
Thanks for the release, great! 😄 We have some tests failing now with the updated version. Didn't get a chance to have a look yet, but just to already raise some awareness here. |
Since secp256k1 v4.0 use the N-API, this can avoid some unexpected situations similar to when worker_thread calls binding and use Pure JS version
Try the following code, and run with
secp256k1@3.8
andsecp256k1@4.0
, you will find that in the worker_thread, the error caused byModule did not self-register
will cause its performance to decrease due to the implementation of the JS version