ipfs-shipyard / ipfs-shipyard/pm-idm
Discuss "Identity profile"
- Dominant language
- No language data
- Stars
- 64
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
I would like to schedule a discussion & brainstorm session around Identity Profile. Please fill in the doodle so that we can find a good match for the meeting: https://doodle.com/poll/nrrb9mr5u6wz2qft
DIDs gives as globally unique and secure identifier for each identity while Verifiable Credentials augment that DID with information, including personal information and social proofs. This "union" between DIDs and Verifiable Claims is new and is still being spec'ed. The Identity Profile packs all the meaningful information for DApps and other tools to KYC.
Agenda:
1. Discuss privacy around the Identity Profiles: public vs private, principle of Minimum Disclosure. Three different non-exclusive approaches:
- The identity profile is passed just one-time when authenticating; one chooses what to disclose about the identity
- The identity profile is passed when authenticating, alongside a revocable token to retrieve the identity profile in the future; one chooses what to disclose about the identity
- There's a public identity profile that can be fetched at any time by any DApp
- DApps could link any identity profile profile in the data-structures they create, instead of replicating them
- This would also enable us to do a public search/discovery of identities
- Private information is passed via the other 2 strategies
2. All the Verifiable Credentials created in a device should be stored and replicated among others.
- How will they be stored and replicated? Should we use peer-base? Some DIDs, such as uPort, already do this partially, while others don't.
- Devices can be added and removed (revoked) at any time, which is important for encryption
- There's an overlap with https://3box.io/ and [Identity Hub](https://github.com/decentralized-identity/identity-hub) (similar to Textile's cafes)
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by reviewing the agenda and its references to Doodle, 3box, and Identity Hub; concrete decisions on privacy, credential replication, device revocation, and system overlap would be needed before implementation work can be defined.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, distributed-systems, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100