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

Improvement Suggestion #81

Open
yashbhavsar007 opened this issue Dec 12, 2019 · 0 comments
Open

Improvement Suggestion #81

yashbhavsar007 opened this issue Dec 12, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@yashbhavsar007
Copy link

yashbhavsar007 commented Dec 12, 2019

As we can see that under one node many accounts are produced to make it more sensible add the feature like private key or password. So, user can be authorized by the account library only. I know it can be handled on application-level also but adding features like this can make more secure to access cordapp.
Can generate a private key from name or UUID at the time of the creation of account. And add one more function to verify the account. So, we can verify by library function only(function which returns boolean value by verifying the keys).

There is one more question
If we can have a private key feature then how it can be handled with different node and registered accounts with them?
More suggestions are admired

@roger-that-dev roger-that-dev added the enhancement New feature or request label Dec 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants