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

Add poseidon reference implementation (using sage) #67

Closed
tsunrise opened this issue May 16, 2022 · 1 comment
Closed

Add poseidon reference implementation (using sage) #67

tsunrise opened this issue May 16, 2022 · 1 comment
Assignees
Labels
A-cryptography Area: Issues and PRs related to Cryptography A-testing Area: Testing-related Issues and PRs P-low Priority: Low

Comments

@tsunrise
Copy link
Contributor

After #57 is merged, we might consider adding some sage scripts as a reference implementation to make sure the implementation is correct.

Originally posted by @BoyuanFeng in #57 (comment)

@bhgomes bhgomes added this to the v1.1.0 milestone Jun 9, 2022
@bhgomes bhgomes modified the milestones: v1.1.0, v0.6.0 Jun 21, 2022
@bhgomes bhgomes modified the milestones: v0.6.0, v1.0.0 Jul 1, 2022
@bhgomes bhgomes added P-low Priority: Low A-cryptography Area: Issues and PRs related to Cryptography A-testing Area: Testing-related Issues and PRs labels Jul 6, 2022
@bhgomes bhgomes assigned SupremoUGH and unassigned tsunrise Aug 30, 2022
@SupremoUGH
Copy link
Contributor

Closed. Poseidon consists of multiple rounds, split into full and partial rounds. The hardcoded test for those (albeit not generated by a sage script) is done in constants.rs in

Each round consists of three steps, namely:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-cryptography Area: Issues and PRs related to Cryptography A-testing Area: Testing-related Issues and PRs P-low Priority: Low
Projects
None yet
Development

No branches or pull requests

3 participants