[Archive] Multiple signups

Embedded Wallets (Web3Auth)
1

:classical_building: Archived Content from Web3Auth Community

This topic was originally posted by githubdiscussions on 12/13/2022.
This content has been migrated from our previous community forum to preserve valuable discussions.

How can I prevent user from signing up 2 (or more) times?
Because every time user signs-up he creates new key, basically destroying the previous one.
Since we are using the keys for the wallet, we obviously do not want the user to be able to destroy the key.
So, how can we make sure that we only let the user signup (create the new key) once?



Originally posted by: altim

Check the discussion at: https://github.com/orgs/Web3Auth/discussions/1062
2

@altim what do you mean he creates a new key? Logging in with the account should always return the same key.



Originally posted by: BboyStatix
3

@BboyStatix
Lets say we have "signup" page where we have Signup button which internally calls tKey._initializeNewKey()
And we have "login" page where we call just tKey.initialize()

Is there a way to check if user already has generated private key? Cause in other way he can go multiple times to Sign Up page and generate as many private keys as he wants (old keys will become invalid as I understand)



Originally posted by: ihor-repela