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

RLN-Relay testnet feedbacks #1069

Closed
15 tasks done
staheri14 opened this issue Aug 10, 2022 · 1 comment
Closed
15 tasks done

RLN-Relay testnet feedbacks #1069

staheri14 opened this issue Aug 10, 2022 · 1 comment
Assignees
Labels
track:rln RLN Track (Secure Messaging/Applied ZK), e.g. relay and applications

Comments

@staheri14
Copy link
Contributor

staheri14 commented Aug 10, 2022

Created this issue to track comments collected from on-chain rln-relay testnet.

Write up edits: (corresponding PR #1068)

  • (G) one screenshot has "endpoint" and "secret" in clear, while in the next one are blurred
  • (G) there is an extra line after the first registration command
  • Hiding the membership index so that users know they need to input their own index
  • Spacing inconsistency in the chat2 commands
  • Emphasize that the ethereal client address should be a web socket address

Rln credentials (corresponding PR #1080)

  • (R) Updating the tutorial to signify that RLN credentials are being persisted in a separate file. Otherwise, all the chat2 instances read and use the same credentials.
  • (G) warn users with a message when a local credential file is loaded, specifying that no membership regsitration was executed.
  • (G) Allow re-registration even when the rlncredentials.txt file is present. Maybe via an extra parameter --force-registration=true ((S)the cleanest path would be to just rely on one input path, either the file or cli arguments, but not both.)
  • (R) Allowing multiple rlnCredentials.txt files for distinct chat2 apps running on the same machine. Potentially prefixing the filenames with the Ethereum account address (good but not sufficient)

Chat interface: (corresponding PR #1082)

  • (R) It would be nice to see an indication that a message you are sending is considered spam. The only way to know is by opening two chat2 apps and seeing that one does not receive the messages from the other
  • (R) After rln-relay preparation is in progress ..., print a link to etherscan to see the transaction details

Error handling:

  • (F) chat2 should handle the error when a http address for the Ethereum client address is passed instead of printing the unhandled exception
  • (F) Validate RLN credentials and let the user know if invalid. no longer valid since we removed the manual rln credential config option and replaced it with a file, so the code write and reads the data to/from a file with no user intervention
  • (R) Proper error handling when using an account without funds
  • (G) Resources are not released when chat2 is terminated by ctrl+c, this should be fixed. seems already supported

Requested features:

Out of scope

Future

@staheri14
Copy link
Contributor Author

Closing the issue as the testnet comments are either addressed or captured in a tracking issue.

Repository owner moved this from Now/In Progress to Done in Vac Research Sep 1, 2022
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