Base layer for decentralized identity and verifiable credentials
Developers create and verify DIDs and credentials on the network through our layer.
Stack and topics
| Industry | Digital identity |
|---|---|
| Region | Global |
Context
The client and the problem
Developers on a public blockchain had no standard way to issue, resolve and revoke decentralised identities and credentials. Each product that needed identity had to build its own, and none of them worked together.
The network needed a base layer that any developer can integrate: create a DID, resolve it with standard tools, and issue verifiable credentials against it.
What we built
What did we build?
We built that base layer, from research to the MVP and the full product.
- DID lifecycle. Infrastructure to create, update and revoke DIDs on the network.
- Universal Resolver. Resolution of DIDs through the Universal Resolver, so standard identity tools can read them.
- Verifiable credentials. Issuing verifiable credentials that developers integrate into their own products.
- Services and operations. Smart contracts, Java and Node services, an Angular front end, and AWS, Docker and Kubernetes for operations.
How we worked
Team and process
The team: solution architect, business analyst, senior full-stack, back-end and DevOps engineers and a quality analyst. Work ran from research and an MVP to overall product development.
Facts
Project facts
| Fact | Detail |
|---|---|
| Client | A public blockchain network |
| Our role | R&D, MVP, overall product development |
| Team | Solution architect, business analyst, full-stack, back-end, DevOps, QA |
| Stack | Smart contracts, Java, Node, Angular, AWS, Docker, Kubernetes |
Result
Where it stands
Developers create and verify DIDs and credentials on the network through our layer.
Next step
Building something similar?
A 30 minute call with Oleg. You leave with a clear view of scope, risks and the next step.
Oleg Pun
CEO, Vareger
