Skip to content
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

common/crypto/signature: Use a newer version of ECVRF #4838

Closed
1 of 2 tasks
Yawning opened this issue Jul 7, 2022 · 1 comment · Fixed by #4668
Closed
1 of 2 tasks

common/crypto/signature: Use a newer version of ECVRF #4838

Yawning opened this issue Jul 7, 2022 · 1 comment · Fixed by #4668
Assignees
Labels
c:beacon Category: random beacon service c:breaking/consensus Category: breaking consensus changes c:breaking Category: breaking code change

Comments

@Yawning
Copy link
Contributor

Yawning commented Jul 7, 2022

When I implemented ECVRF in curve25519-voi, the IETF draft was less than version 11. As of version 11, after leaving things largely unchanged for years, they broke proof backward compatibility.

  • The next time we bump the curve25519-voi import, switch to using the v10 backward compatible proof/verify routines. (go: Bump the curve25519-voi import #4839)
  • Whenever we can jettison beacon state (so a dump-restore hard fork) switch to using the v13 style proofs.
@Yawning Yawning added c:breaking/consensus Category: breaking consensus changes c:beacon Category: random beacon service c:breaking Category: breaking code change labels Jul 7, 2022
@Yawning Yawning self-assigned this Jul 7, 2022
@Yawning
Copy link
Contributor Author

Yawning commented Jul 7, 2022

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c:beacon Category: random beacon service c:breaking/consensus Category: breaking consensus changes c:breaking Category: breaking code change
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant