Skip to content

Conversation

real-or-random
Copy link
Collaborator

This also enables a test that was failung due to the parity bug.

This also enables a test that was failung due to the parity bug.
Copy link
Member

@tcharding tcharding left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Legend!

ACK f419fe8

@elichai
Copy link
Member

elichai commented Jun 16, 2022

Could you explain why in other places it does check the 32'nd byte but here the 64?
Thanks

@real-or-random
Copy link
Collaborator Author

@elichai
See #435 (comment)

Or are you saying there's another place where it should be changed to 64? Do you want me to add a comment or change the commit message to explain this?

@elichai
Copy link
Member

elichai commented Jun 16, 2022

That was exactly the context I've missed, Thanks!

Copy link
Member

@elichai elichai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK f419fe8

Copy link
Member

@apoelstra apoelstra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK f419fe8

@apoelstra apoelstra merged commit 1c4dd0d into rust-bitcoin:master Jun 16, 2022
chain-forgexcr45 added a commit to chain-forgexcr45/rust-secp256k1 that referenced this pull request Sep 28, 2025
…r in fuzzing

f419fe884bc3a0998a2564a78b752bb24a31330d Fix getting parity from keypair in fuzzing (Tim Ruffing)

Pull request description:

  This also enables a test that was failung due to the parity bug.

ACKs for top commit:
  tcharding:
    ACK f419fe884bc3a0998a2564a78b752bb24a31330d
  elichai:
    ACK f419fe884bc3a0998a2564a78b752bb24a31330d
  apoelstra:
    ACK f419fe884bc3a0998a2564a78b752bb24a31330d

Tree-SHA512: bec00d517495cf010c37079e3d71f1d9547a319aac50cecbca74e6d62eca7188aa79d61ee3d50ef81512c30a31b61b947e2f19e45a95b1b17a1f5cf7cf3f1019
william2332-limf added a commit to william2332-limf/rust-secp256k1 that referenced this pull request Oct 2, 2025
…r in fuzzing

f419fe884bc3a0998a2564a78b752bb24a31330d Fix getting parity from keypair in fuzzing (Tim Ruffing)

Pull request description:

  This also enables a test that was failung due to the parity bug.

ACKs for top commit:
  tcharding:
    ACK f419fe884bc3a0998a2564a78b752bb24a31330d
  elichai:
    ACK f419fe884bc3a0998a2564a78b752bb24a31330d
  apoelstra:
    ACK f419fe884bc3a0998a2564a78b752bb24a31330d

Tree-SHA512: bec00d517495cf010c37079e3d71f1d9547a319aac50cecbca74e6d62eca7188aa79d61ee3d50ef81512c30a31b61b947e2f19e45a95b1b17a1f5cf7cf3f1019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants