We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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
RLN=true
The text was updated successfully, but these errors were encountered:
We can deploy the changes to the test fleet, after the contracts have been redeployed, right? cc: @s1fr0 @staheri14
Sorry, something went wrong.
rlnIdentifier
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.
wakuv2.test
wakuv2.prod
No branches or pull requests
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
RLN=true
compile with zerokit by defaultThe text was updated successfully, but these errors were encountered: