-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat: generic chunked aes nivc #44
Conversation
ff6241c
to
e18a2b7
Compare
if(i == 0) { | ||
hash = PoseidonChainer()([step_in[0],packedPlaintext[i]]); | ||
} else { | ||
hash = PoseidonChainer()([hash, packedPlaintext[i]]); |
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 doesn't look constrained properly? i'm curious about r1cs size as well because this was the exact reason of increased size
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.
Wdym?
what if i want to do 15 folds in a 2 chunk AES? is that possible or we have to add 2 different circuits to the ROM? so |
suggestion from Sambhav Co-authored-by: Sambhav Dusad <[email protected]>
I think we'd probably pick an optimal size be it 2,4,8 chunks at a time, then always have a single chunk circuit as backup to fill in the remainder. |
As of the last changes we have: |
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.
epic cooking, merging this. we inch closer every second!!
Implements a foldable AES GCTR for arbitrary amount of chunks. Tested with both 1 and 2 chunk mode.