-
Notifications
You must be signed in to change notification settings - Fork 1
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
Slowness to generate proofs with recent zerokit versions #66
Comments
My understanding is that in this issue we should:
@richard-ramos is it correct? |
Indeed, but i'm not entirely sure we'll be able to mitigate the issue on JS side as it seems to have been introduced in zerokit |
@tyshko-rostyslav any idea why this is happening? |
If indeed this commit vacp2p/zerokit@5eb98d4 is the reason, it's quite odd, nothing special is happening there |
@tyshko-rostyslav is it possible the move from ark-circom 0.3.0 to 0.4.0 is the problem? |
There was a significant slowdown, when we changed versions, specifically a lot of operations became compressed. As you've seen in this thread, I tried uncompressed versions in ark-circom 0.4, which somewhat helped, but not to the desired effect |
right, I think it'd be more performant if js-rln used a similar approach to https://github.com/Rate-Limiting-Nullifier/rlnjs, maybe even use the package to avoid de-duped work. ofcourse, they use rln-v2, but an older commit will be your best bet |
I need to look into how we can leverage https://github.com/Rate-Limiting-Nullifier/rlnjs |
Ice boxing this task as in future we might have a light weight way of generating / verifying proofs. Potentially we can use parts of @adklempner @waku-org/js-waku-developers |
As described in these comments:
The time to generate a proof increased a lot going from ~3s to ~23s, with this commit vacp2p/zerokit@5eb98d4 introducing the slowness
The text was updated successfully, but these errors were encountered: