You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Understanding the arguments pro/con coordinates from #817...
For a generic-ish Frost implementation, I have need to determine if the output of distributed keygen has even y-coordinate, to perform the Taproot adjustment. I can get away with a local AffineYCoordinateParity trait (fn has_even_y(&self) -> bool) that I implement on k256 and bound on, but maybe "for symmetry" it wouldn't be that horrible to add either AffineYCoordinate or at least AffineYCoordinateParity to the AffineArithmetic::AffinePoint bounds?
The text was updated successfully, but these errors were encountered:
Understanding the arguments pro/con coordinates from #817...
For a generic-ish Frost implementation, I have need to determine if the output of distributed keygen has even y-coordinate, to perform the Taproot adjustment. I can get away with a local
AffineYCoordinateParity
trait (fn has_even_y(&self) -> bool
) that I implement onk256
and bound on, but maybe "for symmetry" it wouldn't be that horrible to add eitherAffineYCoordinate
or at leastAffineYCoordinateParity
to theAffineArithmetic::AffinePoint
bounds?The text was updated successfully, but these errors were encountered: