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

Feature Request: Login using the KYC approved Gladius accounts created during ICO #97

Open
0xNode7 opened this issue Sep 17, 2018 · 1 comment
Labels
enhancement New feature or request

Comments

@0xNode7
Copy link

0xNode7 commented Sep 17, 2018

Instead of entering name and email address at the start of gladius node manager and essentially creating a new account (and then creating a new ethereum account), it would ask you to enter username and password, and these would be the same as the KYC approved account login we have made during the ICO. This way, each account is verified, secure, and connected to a real user instead of bots. This also allows for a single user to login to multiple devices.

Once logged in, we would have another option to either import our own private key/json file and open an existing ethereum account, or create a new one. if we decide to create a new one, we can find where its private key/json file is stored because we should have full control of our own wallets. And these wallets can be changed at any time once logged in, so no ethereum account is permanently bound to a specific user, it is only linked whilst active on the gladius node.

@0xNode7 0xNode7 changed the title Login using the KYC approved Gladius accounts created during ICO Feature Request: Login using the KYC approved Gladius accounts created during ICO Sep 17, 2018
@gladius-bot gladius-bot reopened this Sep 25, 2018
@overtfuture
Copy link
Contributor

We will be looking into a better way to handle this in the future. The one thing I can say in the meantime about accounts is that we will not have a traditional account system with username and password because of the decentralized pools users can join. My initial thought to bring this type of request into our system would be to create a master wallet that we KYC that can spawn accounts for multiple nodes / computers. The reason we cannot have a traditional login is because we do not have or want to create a central login server. We are bypassing that by using the ETH wallets as profiles. Hope this give a bit more insight and I'll flag this as an enhancement to keep for future reference.

@overtfuture overtfuture added the enhancement New feature or request label Dec 6, 2018
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

3 participants