- From: Andrew Hughes <andrewhughes3000@gmail.com>
- Date: Fri, 16 Nov 2018 11:39:52 -0800
- To: nathan.mk.aw@gmail.com
- Cc: indy@lists.hyperledger.org, "W3C Credentials CG (Public List)" <public-credentials@w3.org>
- Message-ID: <CAGJp9UZrz504DnCstHTHP4b2zmw5KK6BrBhhXcrO0bnM-p9i1A@mail.gmail.com>
Not up to speed on the intricacies of Zooko's triangle. But the approach you propose looks lots like existing approaches and new approaches in Identity Proofing/Verification (binding of entity to authenticators) and specifications like FIDO Alliance (local generation and management of asymmetric keys - often using a device-based biometric match to 'unlock' the local key manager/store). *Andrew Hughes *CISM CISSP *In Turn Information Management Consulting* o +1 650.209.7542 m +1 250.888.9474 1249 Palmer Road, Victoria, BC V8P 2H8 AndrewHughes3000@gmail.com *https://www.linkedin.com/in/andrew-hughes-682058a <https://www.linkedin.com/in/andrew-hughes-682058a>* *Digital Identity | International Standards | Information Security * On Fri, Nov 16, 2018 at 10:14 AM 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. > > 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 Friday, 16 November 2018 19:40:26 UTC