Imagine an ‘Oh, yeah?’ button on your browser. There you are looking at a fantastic deal that can be yours just for the entry of a credit card number and the click of a button. "Oh, yeah?", you think. You press the ‘Oh, yeah?’ button. You are asking your browser why you should believe it. It, in turn, can challenge the server to provide some credentials: perhaps, a signature for the document or a list of documents that expresses what that key is good for. Those documents will be signed. Your browser rummages through with the server, looking for a way to convince you that the page is trustworthy for a purchase. Maybe it will come up with an endorsement from a magazine, which in turn has been endorsed by a friend. Maybe it will come up with an endorsement by the seller's bank, which has in turn an endorsement from your bank. Maybe it won't find any reason for you to actually believe what you are reading at all.
From Realising the Full Potential of the web by Tim Berners-Lee
In this blog I’ll be deconstructing three projects every week that’ll take us closer to this vision. I’ll be analysing privacy, trust, computation cost/storage, performance and other UX assumptions of these projects. Assumptions that can potentially hinder or accelerate the growth of them. Here is a preview of projects in ZK identity landscape I’m going to cover:
Verifiable https:
Verifiable email:
Verifiable passport:
Verifiable group membership:
Issuing verifiable credentials:
If you think I missed any project, do drop me a message.