-
Notifications
You must be signed in to change notification settings - Fork 53
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
bug: (rln-relay) chat2 displays zero'd keys #1221
Comments
Thanks for reporting the issue! These set of parameters are deprecated, the rln credential is supposed to be re-used using the credential file path |
Can you please check it with the credential path and let me know if there is still any issue? We shall remove those config options to avoid confusion. |
The fix would be to remove those config options i.e.,
|
Shall it be removed then?
How do I generate the file? what format does it have? |
No need to generate, you only need to pass a path to the file, the code will generate it for you. e.g., |
Yes, for sure. |
Is there an RFC for this format (see vacp2p/rfc#543)? |
Fixed in #1258 |
Problem
When starting
chat2
with existing RLN credentials, it shows the following message:Instead of the passed RLN Credentials
Impact
Confusion for the user as message sent seem to have a proof attached:
To reproduce
nwaku version/commit hash
7874644
Built with
RLNZEROKIT=true
The text was updated successfully, but these errors were encountered: