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

Add Friend List - to help send/receive with friends easier #23

Open
totiz opened this issue Jul 31, 2019 · 4 comments
Open

Add Friend List - to help send/receive with friends easier #23

totiz opened this issue Jul 31, 2019 · 4 comments

Comments

@totiz
Copy link
Contributor

totiz commented Jul 31, 2019

No description provided.

@totiz totiz changed the title Add Friend List Add Friend List - to help send/receive with friends easier Aug 2, 2019
@totiz
Copy link
Contributor Author

totiz commented Aug 2, 2019

Motivation
This's an open discussion for friend list feature, You can thinks this feature as the same as we have with facebook messenger. That allow you to send messages to friends without knowing their email address, this's the same think that you can can send Libra Coin (LIB) to friends without knowing their full address.

Open for discussion

  1. Should we have add friend button with property like this?
  • Full address (mandatory)
  • Nick name (mandatory)
  • Country (optional)
  1. Or should we create my profile and share the profile QR with my friends that they can easily add me to contact list without filling anything?
  2. Should we show friend nick name on transaction history instead of full address?
  3. Should we have new standard QR that allow sender to scan and getting info like nick name, full address, then sender and transfer to that QR or add to sender contact list?
  4. Or any suggestion please share.

@suraneti
Copy link
Contributor

suraneti commented Aug 5, 2019

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?

@totiz
Copy link
Contributor Author

totiz commented Aug 5, 2019

@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).

@Nokomy
Copy link

Nokomy commented Oct 15, 2019

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...
We need to increase the richness in features option available...Let's give it a mind mapping approach...

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.
And the options for users educational mode in wallet's settings and the next level is experience with a wallet assistant options mode(*),....when setting up LIBRA for the 1st time, not assuming any user has the knowledge at-all about Cryptos.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants