-
Notifications
You must be signed in to change notification settings - Fork 89
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
Signing key management #30
Comments
We can simply keep the encrypted EdDSA keys in local storage of the browser. Keys can be discarded when the funding round ends. 3box option is interesting but it is needed only if there are users who access dapp from multiple devices. |
@xuhcc for milestone 3, I assume we're just rolling with the current local storage solution? |
@auryn-macmillan Yes, for now we will store the encrypted key in local storage. The dapp asks user to sign a message at log in. This signature is then used to create a secret key which encrypts the data using AES. I'll publish the code soon for review. |
Add recipient transaction on form submission
Users need a way to store their MACI message-signing keys
3box? Ceramic?
The text was updated successfully, but these errors were encountered: