keybase / keybase/keybase-issues
Keybase as trusted identity provider?
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
I don't know if it's in the roadmap for Keybase, but I would love to see some kind of permissions model around your identity similar to, but STRONGER than Facebook/Google/LinkedIn, where you could allow other parties access to more of your information than just your public description via a delegation. You could use this as an online "backup" of your personal information, encrypted via the private key(s) from your profile, and the site generates new individual subkeys to allow a user/entity to access bits of information about you (eg. your bitcoin wallet address or see your EIN, if you are operating a development business and it is required for a form like the 1099 if you are contracting somewhere).
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue is a high-level proposal for delegated access to personal information through Keybase identities, including encrypted backups and per-entity subkeys. No files, tests, or entry points are named; first clarify the scope and intended permissions model with maintainers before implementation. Done would require an agreed design and an identified implementation path.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, authorization, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100