-
Notifications
You must be signed in to change notification settings - Fork 8
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
RLN: Update identity_secret generation #81
Comments
cc: @AtHeartEngineer from the PSE team |
Thanks for the issue. I think was fairly agreed that we want to generate credentials as described in semaphore so that we have compatibility. The only thing I'd like to know is if we want to keep current keygen implementation (that computes Given that changing current keygen implementation implies a refactor of zerokit, nwaku, go-waku, rln-wasm, etc. we could probably add a new API to allow smooth transition and then, in case, deprecate the old keygen. |
Agreed! |
@cedoor FYI |
This would require a spec change right? If so we should have an issue and discussion/decision in RFC repo |
I don't think this requires a spec change. The previous implementation was not according to spec, and now it is :) |
To make the credentials generated by RLN more compatible with Semaphore, we need to update the secret generation to include generation of the
identity_trapdoor
andidentity_nullifier
as mentioned in Semaphore's docs - https://semaphore.appliedzkp.org/docs/technical-reference/circuitsThis will allow re-using the same credentials for Semaphore groups and RLN
cc: @s1fr0 @oskarth
The text was updated successfully, but these errors were encountered: