I’ve been working on a couple of projects that we’re considering for integration with Sovrin, or Hyperledger Indy. This is an excellent framework for managing a cross-application identity, and for securely storing and sharing identity-related information. The two applications are within the social sector:
- One application is related to service delivery for the homeless, and leverages Sovrin/Indy’s capabilities to support “Guardianship”, or the ability for an organization to act as a steward for the identity for individuals who are not able to self-manage;
- Another is for volunteer recruiting in the non-profit space, and leverages “Verifiable Claims” to provide assurances regarding the credentials of both the volunteers and the service organizations.
I’ll blog more about the specifics of each project in the future.
One challenge in working with either Sovrin or Hyperledger Indy right now is that the code, which was originally developed as the Sovrin Network, is now in the process of transition to the Hyperledger Indy project. Which means, depending on when you read this post, the documentation is in a state of flux, and the code is also in a transitional state. There are a number of “Indy” projects within Hyperledger, and it’s not clear how to get a network up and running.
Fortunately, https://github.com/brycecurtis/indy-tutorial-sandbox has come to the rescue with a set of Docker-based scripts that can quickly get a local network up and running. (I have also cloned the repository at https://github.com/ianco/indy-tutorial-sandbox to support some additions I am planning in the near future.) The instructions are pretty clear, so I won’t add too much information, other than the basic sets of instructions to follow are at:
- https://github.com/ianco/indy-tutorial-sandbox/readme, for the instructions on setting up the Indy network
- https://github.com/hyperledger/indy-node/blob/stable/getting-started.md, for running the “Alice” demo (using the local network to run through a scenario of applying for a job, loan etc.)
The script creates an “indy-base” Docker image of the main Indy node by cloning and building the “indy-node” project. The script then starts up a 4-node Indy network, running 4 instances of “indy-base”, and seeding the network with identities for our clients (Faber, Acme and Thrift). The script then starts agents for these organizations, as well as a client node for Alice.
I’ll get into more of the technical details behind this Sovrin/Indy demo in future posts.