-
Notifications
You must be signed in to change notification settings - Fork 419
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
Feature Request: Asymmetric Encryption #691
Comments
There is no exposed asymmetric encryption/decryption in sr25519. See polkadot-js/common#633 |
I see.. |
This issue has been open for 21 days with no activity and is not labelled as an enhancement. It will be closed in 7 days. |
This issue has been open for 21 days with no activity and is not labelled as an enhancement. It will be closed in 7 days. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query. |
There are some use cases where asymmetric encryption is needed, where the public key is used to encrypt a message, and private key is used to decrypt that message.
Currently this is not possible because there is no API in that lets us use the private key of an account.
Is this something that is possible to be implemented?
I don't mind having a try at this myself if it is.
The text was updated successfully, but these errors were encountered: