Native: remove deprecated NamedCurve enum#3273
Merged
Conversation
3.7.0 (and a batch of 3.7.*) is out, which means that users can see the "Obsolete" warning for NamedCurve enum and migrate to NamedCurveHash. Close #3236. Signed-off-by: Anna Shaleva <shaleva.ann@nspcc.ru>
Jim8y
reviewed
May 24, 2024
Jim8y
approved these changes
May 24, 2024
vncoelho
reviewed
May 24, 2024
Member
No, Its the same method as before with different parameters and defaults. |
shargon
approved these changes
May 26, 2024
cschuchardt88
approved these changes
May 26, 2024
superboyiii
approved these changes
May 27, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
3.7.0 (and a batch of 3.7.*) is out, which means that users can see the "Obsolete" warning for NamedCurve enum and migrate to NamedCurveHash.
Close #3236. This change does not introduce state difference and does not require node resync, it's fully compatible with the existing networks.
Type of change
How Has This Been Tested?
Checklist: