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: Introduce v2 module #1764
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The freeze commit needs to also update the root module go.mod
to reference dcrec/secp256k1/v1.0.2
so it will include the latest.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The introduce v2 module commit also needs to update the references within the module itself to point to v2. Namely, in example_test.go
and genprecomps.go
.
Everything else looks good.
This serves as the final release of version 1 of the dcrec/secp256k1 module. All future releases will be moving to version 2 of the module.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was doing another rounds of tests to be sure and realized I approved this a bit too hastily. The schnorr
package is still importing the v1 module despite being part of the v2 module. All of the imports in the schnorr/*.go
files need to be updated to import "github.com/decred/dcrd/dcrec/secp256k1/v2"
in the secp256k1: Introduce v2 module
commit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The latest changes resolve the last outstanding issue. Looks good.
No description provided.