In the scope of this issue


To be addressed later on
[ ] add public key for an account?
[ ] add Privacy policy to the bottom of the screen?
[ ] ENS name should be shown there if user has it?
Current screen

nightly 6 Sep 2019, device - Samsung S10 Android 9
@rachelhamlin we can make it bounty when it is finalized from design POV , right?
I'm going to remove the v1 release label for this one because:
Unlock screen - not showing public key here any more. Is that a bug?
Eric: We had a conversation about it with Hester. It鈥檚 actually something that might change. We might allow users to have multiple chat keys.
The root key will always be the same, or it could be an identifier. I leave it to design to think about which one is best.
@andmironov would you want to spend some time working on that piece? Either 1) an identifier for your public key to differentiate your various random names, or 2) just the root key (whichever bit will be the same regardless of how many chat keys you are ultimately managing).
I'm not quite sure what the benefit is of displaying the public key here though. I suppose it's helpful to differentiate your accounts, if you have a bunch of random names.
But the whole point of multi-account is that you only need one Status account, right?
If it's possible I'd add the following changes to this screen:


cc @rachelhamlin do you think this might make it to v1 after all?
@andmironov the changes proposed in your comment are quite simple, so probably. Though I don't view them as urgent, so will put a bounty on. I think they'll get done.
I'd like to return to the ENS and public key issues later. Going to create a separate issue for your comment.
Edit: Jokes, just updated this same issue. Added to bounty queue.
@rachelhamlin I think now it is part of https://github.com/status-im/status-react/issues/9224
Should we close this one?
Yup, think so, thanks @churik