-
Notifications
You must be signed in to change notification settings - Fork 554
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
feat(crypto)!: remove sr25519 curve #3646
Conversation
looks like no one is actually using it
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.
Legit.
But I think we should deprecate this key type in v1.x
.
Why? To give a chance to migrate? If they are using it w/ 0.38 line, then they would be able to continue using it for at least 1 year. Not sure we want to support sr25519 (in v1) for 2 years. |
looks like no one is actually using it --- #### PR checklist - [x] Tests written/updated - [x] Changelog entry added in `.changelog` (we use [unclog](https://github.com/informalsystems/unclog) to manage our changelog) - [x] Updated relevant documentation (`docs/` or `spec/`) and code comments - [x] Title follows the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) spec (cherry picked from commit ab5b20a) # Conflicts: # crypto/sr25519/privkey.go # test/e2e/generator/generate.go # test/e2e/pkg/testnet.go
Ok, you got a point. But if some asks for it, we need to re-introduce. |
looks like no one is actually using it --- #### PR checklist - [x] Tests written/updated - [x] Changelog entry added in `.changelog` (we use [unclog](https://github.com/informalsystems/unclog) to manage our changelog) - [x] Updated relevant documentation (`docs/` or `spec/`) and code comments - [x] Title follows the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) spec <hr>This is an automatic backport of pull request #3646 done by [Mergify](https://mergify.com). --------- Co-authored-by: Anton Kaliaev <anton.kalyaev@gmail.com>
looks like no one is actually using it
PR checklist
.changelog
(we use unclog to manage our changelog)docs/
orspec/
) and code comments