Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Research Keri - A New Solution for Self-Certifying Identifiers #40

Open
wip-abramson opened this issue Oct 26, 2020 · 0 comments
Open
Labels
Priority: 2 - High 😰 Should be fixed as quickly as possible, ideally within the current or following sprint Type: Research 🔬 When further investigation into a subject is required

Comments

@wip-abramson
Copy link
Member

What?

Keri stands for Key Event Receipt Infrastructure that seems promising. It enables the creation of public and private identifiers that do not necessarily have to be rooted to a distributed ledger. It may be more flexible and hence desirable for OM usecases.

Looking for someone to really dive into this, ideally attending this weekly call - https://identity.foundation/working-groups/identifiers-discovery.html at 4pm CET.

Code is currently in development in a number of different languages and it would be great to get a sense of what Keri is capable of both today and as the project progresses.

How long?

Initially 3-6 months

Is your research related to a problem?

To be able to leverage public-key cryptography we need a key management solution that is scalable and secure, providing a means for identifiers correlated to entities and trusted. Keri seems like a promising solution.

Additional Context

There are plenty of resources to get started, this is a pretty comprehensive list:

Libraries in development:

@wip-abramson wip-abramson added Type: Research 🔬 When further investigation into a subject is required Priority: 2 - High 😰 Should be fixed as quickly as possible, ideally within the current or following sprint labels Oct 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: 2 - High 😰 Should be fixed as quickly as possible, ideally within the current or following sprint Type: Research 🔬 When further investigation into a subject is required
Projects
None yet
Development

No branches or pull requests

1 participant