Skip to content
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

Closed
3 of 4 tasks
oskarth opened this issue Aug 5, 2022 · 5 comments
Closed
3 of 4 tasks

Enable Zerokit by default #1061

oskarth opened this issue Aug 5, 2022 · 5 comments
Labels
blocked This issue is blocked by some other work track:rln RLN Track (Secure Messaging/Applied ZK), e.g. relay and applications

Comments

@oskarth
Copy link
Contributor

oskarth commented Aug 5, 2022

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:

Acceptance criteria

  • Zerokit enabled by default

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.

@oskarth oskarth added blocked This issue is blocked by some other work track:rln RLN Track (Secure Messaging/Applied ZK), e.g. relay and applications labels Aug 5, 2022
@s1fr0
Copy link
Contributor

s1fr0 commented Aug 22, 2022

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 rln-contract branch where the Circom constants are loaded in place of Kilic's ones and then check if the returned hashes correspond to the ones given by Circom implementation.

@staheri14
Copy link
Contributor

staheri14 commented Aug 22, 2022

@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!

@staheri14 staheri14 moved this to Next/Backlog in Vac Research Aug 24, 2022
@staheri14
Copy link
Contributor

staheri14 commented Oct 14, 2022

What is the state of this issue? I guess it needs some updates @s1fr0

@staheri14
Copy link
Contributor

If zero-kit gets enabled by default, it will help resolving this issue as well #1213

@s1fr0
Copy link
Contributor

s1fr0 commented Oct 14, 2022

Zerokit is enabled by default since release v.0.12. Kilic's library is still supported and can be enabled by passing KILICRLN=true instead of RLN=true (which now enables, instead, zerokit RLN).

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.

@s1fr0 s1fr0 closed this as completed Oct 14, 2022
Repository owner moved this from Next/Backlog to Done in Vac Research Oct 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked This issue is blocked by some other work track:rln RLN Track (Secure Messaging/Applied ZK), e.g. relay and applications
Projects
None yet
Development

No branches or pull requests

3 participants