I’ve read Ethereum will make possible cryptographically verifiable identities that are integrated with the Ethereum client, and thus not requiring any password or logins.

Does this presuppose the the user is using the Mist browser? Are there any proposed design patterns we make apps for the regular web that leverage some of the cryptographic niceties that Ethereum offer (mappings, for instance).

closed as too broad by niksmac, eth Apr 14 '16 at 1:33

Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • define "cryptographically verifiable identity"? – VoR0220 Apr 13 '16 at 20:40
  • are you talking about a reverse turing test? – VoR0220 Apr 13 '16 at 21:42
  • i'm referring to the statement that there's no need to log in to dapps – max Apr 15 '16 at 14:35
  • i'm sorry for being a bit unclear. i found a video example of the identity handling functionality i was referring to: youtube.com/watch?v=Ij5tGo8cp80 (starts at 6:50) here we have a button that changes it's appearance and function based on the account we have selected in mist. I'm trying to understand how to use this in my dapp project. – max Apr 16 '16 at 14:41