-
Notifications
You must be signed in to change notification settings - Fork 6
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
Poseidon starky #16
Poseidon starky #16
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Outside of my concern about Poseidon2 instead of Poseidon1. Everything looks fine; I suspect any unused code that exists presently are waiting to be used in recursion.
} | ||
|
||
let stark = S::default(); | ||
let trace = generate_poseidon_trace(&step_rows); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is Poseidon2. Poseidon2 for plonkish circuits should be taken into built in speed ups that are not present in Poseidon1. So, I'm not sure this benchmark would yield a fair comparison.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually it's Poseidon. There were a couple naming typos, but the implementation in for Poseidon
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have no issues.
No description provided.