The Indy code base (Indy) is a software ecosystem for private, secure, and powerful identity. Once it is implemented, it puts people — not the organizations that traditionally centralize
identity in charge of decisions about their own privacy and disclosure. This enables all kinds of rich innovation: connection contracts, revocation, novel payment workflows, asset
and document management features, creative forms of escrow, curated reputation, integrations with other cool technologies, and so on.
Indy is based on open standards so that it can interoperate with other distributed ledgers. These start, of course, with public-key cryptography standards. Other important
standards cover things like the format of the identifiers, what they point to, and how agents exchange verifiable claims. Indy also supports a system of attribute and claim schemas
that are written to the ledger for dynamic discovery of previously unseen claim types. Relying parties can make their own entitlement decisions based on schemas with publicly known identifiers.
The Indy project was originally the brainchild of the nonprofit group the "Sovrin Foundation".
What are the most important features of Hyperledger Indy?
First, identifiers on Indy are pairwise unique and pseudonymous by default to prevent correlation. Indy is the first Distributed Ledger Technology
to be designed around Decentralized Identifiers (DIDs) as the primary keys on the ledger. DIDs are a new type of digital identifier that were invented
to enable long-term digital identities that don’t require centralized registry services. DIDs can be verified using cryptography, enabling a digital
“web of trust.” DIDs on the ledger point to DID Descriptor Objects (DDOs), signed JSON objects that can contain public keys and service endpoints for a given identifier.
DIDs are a critical component of Indy’s pairwise identifier architecture.
mix consensus algorithms within the same blockchain.
Second, personal data is never written to the ledger. Rather all private data is exchanged over peer-to-peer encrypted
connections between off-ledger agents. The ledger is only used for anchoring rather than publishing encrypted data.
Third, Indy has built-in support for zero-knowledge proofs (ZKP) to avoid unnecessary disclosure of identity
attributes—privacy preserving technology that has been long pursued by IBM Research (Idemix) and Microsoft (UProve),
but which a public ledger for decentralized identity now makes possible at scale.
Interested in watching a video to learn more about Hyperledger Indy ?