Provable identity. Yes, you can do Oauth via the google or the facebook but sooner or later we need something that isn't tied to getting all your user interaction data ...
Digital notary. So a third person (digitally) signing a transaction or other document exchange.
Haha, my father actually presented me with the idea of a digital notary. He was wondering why we send everything electronically, where one party has to trust the other hasn't faked it, and the other party has to trust that the first party won't misuse it.
Provable identity: you get an email, hi i'm a hiring manager from company X, can we get in touch about job Y, could you please send me your (secret) phone number?
It should be possible for you, the receiver of the email, to check if the email originated at company X.
Digital Notary: this came up in several data privacy discussions. You (A) are in contact with B, but you don't want to send B something like a scan of your passport (e.g. for age restricted services). So you disclose the passport scan to Notary and he sends B the message, the passport was disclosed to me and the person is >21.
Re: passport scan issue: check out what the German ID card[0] does. It's better than the passport scan sending "state of the art" on both security and privacy.
Exactly. "Did this email originate at $server" is what DKIM and SPF are meant to solve and IME they work well. Setting them up is not particularly difficult and there is a wealth of open documentation about it.
The point is "proving" something without showing them the proof. E.g. someone Company X trusts looks at the documents or etc and sends a signed confirmation that they confirm X, Y, and Z about Person A.
The point being that Company X does not have a copy of the sensitive information (and neither the liability of losing it) and the Digital Notary would (in theory) have better procedures for properly deleting or storing the data as needed.
Digital notary. So a third person (digitally) signing a transaction or other document exchange.