-
Notifications
You must be signed in to change notification settings - Fork 79
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
Add key recover interops to neox-2.x #1003
Milestone
Comments
roman-khimov
changed the title
Add Keccak and Secp256k1 to neox-2.x
Add key recover interops to neox-2.x
May 30, 2020
AnnaShaleva
added a commit
that referenced
this issue
Jun 1, 2020
AnnaShaleva
added a commit
that referenced
this issue
Jun 2, 2020
AnnaShaleva
added a commit
that referenced
this issue
Jun 2, 2020
Part of #1003 We have to implement Koblitz-related math to recover keys properly with Neo.Cryptography.Secp256k1Recover interop as far as standard go elliptic package supports short-form Weierstrass curve with a=-3 only (see golang/go#26776 for details). However, it's not the best choise to have a lot of such math in our project, so it would be better to use ready-made solution for Koblitz-related cryptography.
AnnaShaleva
added a commit
that referenced
this issue
Jun 2, 2020
AnnaShaleva
added a commit
that referenced
this issue
Jun 2, 2020
Part of #1003 We have to implement Koblitz-related math to recover keys properly with Neo.Cryptography.Secp256k1Recover interop as far as standard go elliptic package supports short-form Weierstrass curve with a=-3 only (see golang/go#26776 for details). However, it's not the best choise to have a lot of such math in our project, so it would be better to use ready-made solution for Koblitz-related cryptography.
AnnaShaleva
added a commit
that referenced
this issue
Jun 2, 2020
Part of #1003 We have to implement Koblitz-related math to recover keys properly with Neo.Cryptography.Secp256k1Recover interop as far as standard go elliptic package supports short-form Weierstrass curve with a=-3 only (see golang/go#26776 for details). However, it's not the best choise to have a lot of such math in our project, so it would be better to use ready-made solution for Koblitz-related cryptography.
AnnaShaleva
added a commit
that referenced
this issue
Jun 2, 2020
AnnaShaleva
added a commit
that referenced
this issue
Jun 2, 2020
Part of #1003 We have to implement Koblitz-related math to recover keys properly with Neo.Cryptography.Secp256k1Recover interop as far as standard go elliptic package supports short-form Weierstrass curve with a=-3 only (see golang/go#26776 for details). However, it's not the best choise to have a lot of such math in our project, so it would be better to use ready-made solution for Koblitz-related cryptography.
AnnaShaleva
added a commit
that referenced
this issue
Jun 2, 2020
Implement secp256k1 and secp256r1 recover interops, closes #1003. Note: We have to implement Koblitz-related math to recover keys properly with Neo.Cryptography.Secp256k1Recover interop as far as standard go elliptic package supports short-form Weierstrass curve with a=-3 only (see golang/go#26776 for details). However, it's not the best choise to have a lot of such math in our project, so it would be better to use ready-made solution for Koblitz-related cryptography.
AnnaShaleva
added a commit
that referenced
this issue
Jun 2, 2020
Implement secp256k1 and secp256r1 recover interops, closes #1003. Note: We have to implement Koblitz-related math to recover keys properly with Neo.Cryptography.Secp256k1Recover interop as far as standard go elliptic package supports short-form Weierstrass curve with a=-3 only (see golang/go#26776 for details). However, it's not the best choise to have a lot of such math in our project, so it would be better to use ready-made solution for Koblitz-related cryptography.
AnnaShaleva
added a commit
that referenced
this issue
Jun 2, 2020
Implement secp256k1 and secp256r1 recover interops, closes #1003. Note: We have to implement Koblitz-related math to recover keys properly with Neo.Cryptography.Secp256k1Recover interop as far as standard go elliptic package supports short-form Weierstrass curve with a=-3 only (see golang/go#26776 for details). However, it's not the best choise to have a lot of such math in our project, so it would be better to use ready-made solution for Koblitz-related cryptography.
AnnaShaleva
added a commit
that referenced
this issue
Jun 3, 2020
Implement secp256k1 and secp256r1 recover interops, closes #1003. Note: We have to implement Koblitz-related math to recover keys properly with Neo.Cryptography.Secp256k1Recover interop as far as standard go elliptic package supports short-form Weierstrass curve with a=-3 only (see golang/go#26776 for details). However, it's not the best choise to have a lot of such math in our project, so it would be better to use ready-made solution for Koblitz-related cryptography.
AnnaShaleva
added a commit
that referenced
this issue
Jun 3, 2020
Implement secp256k1 and secp256r1 recover interops, closes #1003. Note: We have to implement Koblitz-related math to recover keys properly with Neo.Cryptography.Secp256k1Recover interop as far as standard go elliptic package supports short-form Weierstrass curve with a=-3 only (see golang/go#26776 for details). However, it's not the best choise to have a lot of such math in our project, so it would be better to use ready-made solution for Koblitz-related cryptography.
AnnaShaleva
added a commit
that referenced
this issue
Jun 3, 2020
Implement secp256k1 and secp256r1 recover interops, closes #1003. Note: We have to implement Koblitz-related math to recover keys properly with Neo.Cryptography.Secp256k1Recover interop as far as standard go elliptic package supports short-form Weierstrass curve with a=-3 only (see golang/go#26776 for details). However, it's not the best choise to have a lot of such math in our project, so it would be better to use ready-made solution for Koblitz-related cryptography.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We need to support new interops from neo-project/neo#1597 in our neox-2.x branch. Related to #918 for Neo3.
The text was updated successfully, but these errors were encountered: