-
Notifications
You must be signed in to change notification settings - Fork 281
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
Fix the mess around Parity #370
Comments
My proposed solution:
So I think we can clean this all up with another minor version. |
Just noting that the first step is where we got stuck last time, the naming of |
Hm, isn't it quite obvious: odd should be a first odd integer value - and even should be a first even integer value, i.e. odd is 1 and even is 0. 0 is indeed even, since 0 % 2 == 0, and by definition even are the integers which divide by 2 without reminder. |
I agree that the mapping between 0/1 and even/odd is natural .. I'm not sure how this maps to the 02/03 prefixes on full keys, but I should hope also in the natural way! |
Yeah, in libsecp I'm still somewhat uncomfortable exposing to users that public keys can even be "Even" or "Odd", but maybe this ship has long sailed. |
TIL: Cannot deprecate implementation of
Results in:
|
Recently I opened up a hornets nest by changing the parity boolean into an opaque type (#344). This PR was also flawed, @sanket1729 came to the rescue in #360 and #361.
There has now been much talk and disagreement on this, listing links here in an attempt to collect all the comments (in no particular order):
The text was updated successfully, but these errors were encountered: