1D/ Intro to Hello
Intro to Hellō
Session Convener: Dick Hardt
Notes-taker(s): Steve Venema
Tags / links to resources / technology discussed, related to this session: https: hello.coop
Discussion notes, key understandings, outstanding questions, observations, and, if appropriate to this discussion: action items, next steps:
First part of the session was just people playing around with the live demo from their phones.You use this QR code (pic from the session whiteboard):
QR CODE PICTURE: See image(s) for these notes in the IIWXXXIV Book of Proceedings here:
https://internetidentityworkshop.com/past-workshops/
…which takes you to a webpage that looks like this:
SCREENSHOT: See image(s) for these notes in the IIWXXXIV Book of Proceedings here:
https://internetidentityworkshop.com/past-workshops/
The overall idea here is to allow developers to get their app working with one [proxy] IDP which can, in turn, interact with many different IDPs. I tried the above registration flow and found the prompts a bit confusing regarding what data is being shared with whom and what the trust model looks like.
Business model:
- “Revenue” comes from charging RP’s a few cents per verified claim
- This is in quotes because they only work in a token currency managed through a DAO (Decentralized Autonomous Organization)
- Vision: Resellers can charge real $$’s and convert that money to tokens in the DAO
- 40% of the “production” will go into the DAO (I didn’t fully understand this)
- Dick noted that tokenomics is an area of active development so they don’t specifically focus on this except as a consumer of the emerging tokenomics capabilities
Privacy:
- One of the technical innovations that Dick claimed is around privacy, but the group got sidetracked before this could be enumerated better.
3 components:
- Orchestration service, what the RP hits it, which starts a session
- Looks up the RP info
- User goes to $Google to authenticate
- Gets a token from the token service
- Encryption service
- Storage service
Only the user can manage what is stored relative to that user (for a given IDP i think)
When you first use the service, you become a “member of the cooperative” and are emailed a link to their profile management service interface.