-
Notifications
You must be signed in to change notification settings - Fork 44
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
Add Friend List - to help send/receive with friends easier #23
Comments
Motivation Open for discussion
|
I agree with the first and third topic. If we make social login, how to keep or matching the secret key for the client's social account without store private key in our server? |
@suraneti If we make social login, we should only map public address with social id, but for secret key user need to backup by themselves (and we need mnemonic phrase exporting feature). |
Hello team I have seen your progress and I believe we should follow thru with ensuring high systems integrity in mind ...considering all features for needs, yet the factor for being social with options available however creating design with security or higher to users is very important.... We should allow users have richer options... To my mind it is equal to being options dynamic and user friendly....Since the reasons that triggers clients' adoption and decision be welcoming following trending accepted mode of access to Libra Crypto wallets.... I am expecting Kulap.io wallets would be the last-line of the best options available in wallet types for LIBRA users....the basic features to adjust wallet' levels of heuristic dependability should be allowed to be determined by users... i.New users however the systems does not store password a short video educational on the importance of knowing all the LIBRA wallet's setting must be presented when setting up LIBRA for all new users assuming they are "beginners" with email address not having knowledge of Crypto wallet or history of email/wallet transaction or attachment. ii.Users who owns specific models or type of high end phones like Apple & Samsung...would most like carry out higher volumes of transactions and should be also advised to increase the security levels of there phones and LIBRA wallet's Apps,(as setting option)...assuming they have knowledge of or own Cryptos and wish to use a multiple Crypto + LIBRA wallet or LIBRA stand alone wallet option. iii.New users on very low-end designs of android phone (considering the channels that markets these brands as intro & educational partners)...are more likely to carry out lower volumes transactions however more users, requires security levels of there choices...with warning on every stages when effecting or executing transactions...this group are most like aware of various wallets and devices however decided to settle for economic & functional apps a version that would be in high downloads volumes. iv.New/Returning Users on desktop mode,(Keeping in mind the passphrase or password and the recovery seed phrases can be made available from cloud backup as an option with encryption storage system)...And this version should be allowed to access mainet last transaction process and transactions history and location of change. 4.Trezor or hard-drive storage options for new users and adoption...by higher net worth and institutions... GPS restrictions and Twin lock mode should be initiated. A twin or dual keys(or 2nd access) should be created as options for institutions observing the registered API allocated with GPS restrictions. |
No description provided.
The text was updated successfully, but these errors were encountered: