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

feat: Use zerokit by default/deploy on test fleet #1227

Closed
Tracked by #1061
fryorcraken opened this issue Oct 5, 2022 · 2 comments
Closed
Tracked by #1061

feat: Use zerokit by default/deploy on test fleet #1227

fryorcraken opened this issue Oct 5, 2022 · 2 comments
Labels
track:rln RLN Track (Secure Messaging/Applied ZK), e.g. relay and applications

Comments

@fryorcraken
Copy link
Collaborator

Problem

The Kilic and zerokit RLN implementations are not compatible.

In go-waku, we know use zerokit by default
In the browser (js-waku+js-rln) we can only use zerokit

Which means that browser example such as https://examples.waku.org/rln-js do not work when connecting to the Waku v2 test fleet as kilic is deployed

Suggested solution

  1. Deploy nwaku with zerokit on waku v2 test (and prod for next release)
  2. make RLN=true compile with zerokit by default
@fryorcraken fryorcraken added the track:rln RLN Track (Secure Messaging/Applied ZK), e.g. relay and applications label Oct 5, 2022
@rymnc
Copy link
Contributor

rymnc commented Oct 5, 2022

  1. has been resolved by chore(Makefile): Make zerokit the default RLN implementation #1190

We can deploy the changes to the test fleet, after the contracts have been redeployed, right?
cc: @s1fr0 @staheri14

@rymnc
Copy link
Contributor

rymnc commented Oct 11, 2022

Zerokit has been added to the test fleet and deployed to wakuv2.test at the moment. It will be deployed to wakuv2.prod with the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
track:rln RLN Track (Secure Messaging/Applied ZK), e.g. relay and applications
Projects
None yet
Development

No branches or pull requests

2 participants