Skip to content
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

secp256k1: update func signatures. #934

Merged
merged 1 commit into from
Dec 22, 2017
Merged

Conversation

dnldd
Copy link
Member

@dnldd dnldd commented Nov 30, 2017

This simplifies secp256k1 & schnorr related func signatures by removing the koblitz curve param. The secp256k1 curve is used implicitly instead.

This is work towards #923.

@dajohi dajohi changed the title sec256k1: update func signatures. WIP: sec256k1: update func signatures. Nov 30, 2017
@dajohi
Copy link
Member

dajohi commented Dec 4, 2017

@dnldd rebase required.

@dnldd dnldd changed the title WIP: sec256k1: update func signatures. sec256k1: update func signatures. Dec 5, 2017
Copy link
Member

@davecgh davecgh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please revert the second commit. We don't want ScalarBaseMult checking curve initialization on every invocation.

funcs implicitly use the sec256k1 curve instead of passing it as a
param.
@dnldd
Copy link
Member Author

dnldd commented Dec 22, 2017

@davecgh updated.

@davecgh
Copy link
Member

davecgh commented Dec 22, 2017

Also, I should note that this doesn't completely resolve 923. It is the first step of it. Perhaps change the PR description to include work towards #923?

@davecgh davecgh merged commit 2be3bf6 into decred:master Dec 22, 2017
@davecgh davecgh changed the title sec256k1: update func signatures. secp256k1: update func signatures. Mar 7, 2018
@dnldd dnldd deleted the secp256k1 branch June 4, 2018 23:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants