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

Address book - Separate for each wallet #107

Open
Myke500 opened this issue Sep 10, 2022 · 0 comments
Open

Address book - Separate for each wallet #107

Myke500 opened this issue Sep 10, 2022 · 0 comments
Labels
enhancement New feature or request low priority Something that should be only implemented when more important functions are done

Comments

@Myke500
Copy link
Member

Myke500 commented Sep 10, 2022

Address book can be accessed by all wallets on a single xCore application. (All users the have access to the computer)

Separate address books per wallet would be a better solution in a shared application or shared computer setting.

Make the address book index only available to the wallet the added the address. Other wallets will not be able to see the same addresses added by other wallets(users)

The screenshots show that when using the same computer, running the same application of xCore (containing multiple wallets):
test wallet 2 has 2 addresses added,
however when we look at the address book in test wallet 3 we see that the addresses added from wallet 2 also show up in wallet 3.

Screenshots:
Test wallet 2 Address Book - with 2 addresses added
Screenshot_2

Test Wallet 3 Address Book - No addresses added
Screenshot_3

Additional Context:
This is a low priority issue at this time, it will become more relevant as the user base grows.

@Myke500 Myke500 added enhancement New feature or request low priority Something that should be only implemented when more important functions are done labels Sep 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request low priority Something that should be only implemented when more important functions are done
Projects
None yet
Development

No branches or pull requests

1 participant