Data is immediately actionable — if you trust the source of the credential, you can trust the data.
Data is secure — no need for third parties or to store the data in centralized databases to manage authentication.
Takes the hassle out of data privacy compliance — a person is in control of their data and can share it by consent.
Protect your systems from AI deepfakes with Verifiable Credentials that cannot be replicated by A
Interoperability
Proven provides unmatched interoperability by supporting multiple standards, including AnonCreds, W3C Verifiable Credentials, DIDComm, and emerging standards like SD-JWT and OpenID for Verifiable Credentials (OID4VC).
Global Standards
Proven also complies with global data protection standards including eIDAS, EUDI, and industry specific technology standards. Including W3C Verifiable Credentials, Open Badges 3.0 from 1EdTech, and IATA One ID and ICAO DTC for travel
Customizable Deployments
Proven is designed for flexibility, offering both a SaaS platform model or allowing deployment via APIs in various environments, including on-premise, cloud-based, or hybrid setups
Plug-and-Play Integration
Indicio Proven works seamlessly with the Indicio Network and other decentralized identity ecosystems. It offers pre-built integrations for developers to easily add decentralized identity to their applications.
Privacy-First Design
Proven ensures that users maintain control over their data, aligning with principles of self-sovereign identity (SSI). It supports use cases that comply with data privacy regulations.
Secure Credential Management
Indicio Proven enables full lifecycle management of credentials, including issuance, revocation, and expiration. Organizations can define policies for credential management, ensuring compliance with industry standards and internal requirements for credential authenticity and validity.
Customizable Governance
Users can configure and manage their own trust frameworks, including selecting roots of trust, defining credential schemas, and customizing credential verification logic. This flexibility supports a wide range of use cases, such as identity verification, secure access management, and compliance monitoring
Multi-Tenant Support
A single Indicio Proven instance can support multiple clients (tenants) in a single environment. Each organization can then securely manage its own decentralized identity (DID) configurations, verifiable credentials, and trust frameworks without interfering with other tenants, ensuring privacy and data isolation
Customization and Configuration
Indicio Proven can be configured by each customer to match specific business needs, such as selecting roots of trust, defining credential schemas, and managing the lifecycle of digital identities and verifiable credentials. This flexibility enables various use cases, from KYC processes to digital access management
APIs for external integration
UI for issuance and verification
Customer chat using basic message
Utilizes Zero-Knowledge Proofs (ZKPs) for selective disclosure, ensuring no centralized storage of personal data.
Enhances user privacy and security by allowing individuals to:
Share only the necessary information.
Avoid exposing all personal details.
Tailored for industries requiring high-trust digital credentials,
government, enterprise, and travel sectors.
Proven enables the creation of Trusted Digital Ecosystems for immediately actionable data.
Cloud-agnostic and supports multiple networks,
Allows organizations to build, deploy, scale, and manage Verifiable Credential ecosystems without being tied to a specific cloud provider.
Built on open standards, with community-driven development, ensuring transparency and continuous improvement.
Open-source foundation fosters innovation and collaboration within the decentralized identity community.
Fully customizable — deploy how you choose; customers own their solutions; there is no vendor lock-in
For truly sensitive operations, the workflows involved in presenting this data (in order to impersonate you) can be paired with a liveness check and biometric comparison between the face on an identity credential and one captured by the phone’s camera.
When a device is lost, you can revoke the credentials that are stored in that wallet, making them useless even if the device and wallet are compromised. This is similar to how, if you lose a credit or debit card, you go to the card provider and ask them to turn it off.
The restoration experience, at the most basic level, is to go to the issuers and have the credentials reissued. This is what most credential issuers do today.
High availability: If one node on the network goes down for any reason, there are plenty of others to receive data from.
Geopolitical and infrastructure diversity: By hosting the ledger on servers located in multiple geographic areas and by diverse organizations, network resilience to technical problems is maximized — and this contributes to high availability.
The following information — and only this information — is, typically, stored on the ledger:
DIDs for an Organization, Company, or Institution
These are used to verify credentials from a particular issuer; the endpoint allows you to communicate with that issuer.
Credential Schemas
A credential contains information and Schemas define the different fields containing that information.
Credential Definitions
These are specific to the use of the AnonCreds credential format with Hyperledger Indy. Credential Definitions link a cryptographic key to each of the attributes in a Credential Schema. This allows a holder of a credential to share information in privacy-preserving ways, such as through selective disclosure (only a single attribute is shared) or a predicate proof (an attribute value can be numerically assessed without the actual value being disclosed, such as >21 or <21 for purchasing items that have legal age requirements).
Revocation Registry Accumulators
This provides a way of signaling which credentials are valid by keeping track of which credentials have been revoked and which have not been revoked. The revocation registry accumulator is a way of proving your credential is valid.
Credential Issuance
No information about the issuance of any individual credential is recorded on the ledger.
The Verifiable Credential
Verifiable credentials are not written to or stored on the ledger in any context.
One of the most powerful features of decentralized identity is that you can create an ecosystem of millions of people using millions of credentials with only three or four writes to the ledger: the credential type, the schema, the credential definition, the issuer DID, and the revocation registry
