-
Notifications
You must be signed in to change notification settings - Fork 57
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
Enable Zerokit by default #1061
Comments
Integration will probably require revising/updating round constants of current smart contract Poseidon Hasher implementation so that result aligned with Circom zkSNARK Poseidon circuit. @kgrgpg We might start working on a new |
@s1fr0 it would be very helpful to have an issue in https://github.com/vacp2p/rln-contract covering updates that are needed to be done on the contract, and with pointers to the relevant repos and files e.g., where the Circom constants reside, etc. Thanks! |
What is the state of this issue? I guess it needs some updates @s1fr0 |
If zero-kit gets enabled by default, it will help resolving this issue as well #1213 |
Zerokit is enabled by default since release v.0.12. Kilic's library is still supported and can be enabled by passing Not sure what the second item refers to, since vacp2p/research#126 clearly states that zerokit integration is out of scope. Maybe a new testnet for nwaku with zerokit enabled? I would say that due to preparation of the live demo, all CC extensively tested (and bug-fixed) zerokit not only in nwaku but also in go-waku and js-waku so a preliminary testnet1 can be considered complete. This issue was replaced by #1227 and hence can be closed. |
Problem
We want to use Zerokit by default to have one code base to worry about and pave the way to cross-client testnet.
Notes
Before this can happen, we need the following:
EDIT: merged Zerokit RLN integration in nwaku: alternative approach with inline compilation flag #1060
Acceptance criteria
We can either remove flag in PR that addresses this, or do this at a later stage (depends on confidence around perf etc)
cc @s1fr0 @staheri14 just to capture this future work and its dependencies.
The text was updated successfully, but these errors were encountered: