- From: Melvin Carvalho <melvincarvalho@gmail.com>
- Date: Sat, 17 Nov 2018 09:26:16 +0100
- To: nathan.mk.aw@gmail.com
- Cc: indy@lists.hyperledger.org, W3C Credentials Community Group <public-credentials@w3.org>
- Message-ID: <CAKaEYh+nx1N0X3V=RCXLO3H-3s8JjTuf3PN=N3K8A330OZcdnA@mail.gmail.com>
On Fri, 16 Nov 2018 at 19:14, Nathan Aw <nathan.mk.aw@gmail.com> wrote: > Hi Friends at Indy/w3c, > > I figured that one of the key, perhaps the key, to solving the zooko > triangle theorem/challenge/riddle is to leverage biometric > (retina+fingerprint). > > If there is some way to seamlessly onboard, associate and bind one's DID, > DID Documents and Biometric data (stored in offchain in secure enclaves, > perhaps?), the zooko triangle gordian knot can indeed be solved. > > To-Be Transaction Flow: > 1. Use Biometric to access to this market place app > 2. Fetches all the claims associated with one's biometric identity > 3. Apply jobs, makes purchases seamlessly with the proofs happening behind > the scene. > > Through this, we obviate the need for users to remember lengthy usernames/ > passwords, etc thus achieving the goals of human meaningfulness, > decentralization and security. > > Is this something that is achievable? > > Am keen to work with anyone on this. > Zooko's triangle simply asks whether we can overload a string to do three things. The fallacy is that overloading is a good thing. It's not. It's an anti pattern. Once you see that overloading an identifier to do two things is a bad enough idea, overloading it to do 3 is even worse. So how do you solve the the problem. You use the right identifier in the right place, and use glue aka indexes to link identifiers about. That's the fundamental value add of linked data. And if you look at websites like facebook they solve this use case using 3 different identifiers - Full Name as user facing - Log in with email or phone etc. - Primary key in the graph protocol as your WebID The paradox of Zooko's triangle is that people think it needs solving! > > Thank you. > > Regards, > > Nathan Aw > https://sg.linkedin.com/in/awnathan > > https://www.hyperledger.org/community/technical-ambassador > > > http://www.nasdaq.com/article/guest-post-understanding-the-limits-and-potential-of-blockchain-technology-cm874892 > > > https://www.hyperledger.org/blog/2017/12/05/developer-showcase-series-nathan-aw-ntt-data > > https://bitcoinmagazine.com/authors/nathan-aw/ > > https://twitter.com/Hyperledger/status/938105092644974594 > > > https://www.hyperledger.org/blog/2018/07/24/hyperledger-sawtooth-seth-and-truffle-101 > > https://www.hyperledger.org/persons/nathan-aw > > https://github.com/nathanawmk > > https://erc725alliance.org/ > >
Received on Saturday, 17 November 2018 08:26:50 UTC