Features

Platform, Studio and ADEYA Mobile SDK features

CREDEBL Features

CREDEBL enables end-to-end verifiable credential management with following key features.

User Registration

The platform provides an efficient user registration process through email-based verification. Furthermore, the platform offers modern & highly secure authentication mechanisms such as FIDO Passkey for phishing-resistent user verification. These measures establish a multi-layered approach to user authentication, mitigating the potential for unauthorized access and preserving the security of sensitive user data. Platform also provides highly secure mechanisms such as ClientId and ClientSecret for API authentication.

Organization Onboarding

Facilitates smooth enrolment of organizations into the decentralized identity platform, enabling them to establish a reliable presence and engage in secure digital interactions. This expedites the process for organizations to join the platform.

Team Onboarding

Provides an efficient way to onboard team members for the organization through an email-based invitation. An organization owner can send invitation email to team members to join the platform & the organization.

Wallet for Organizations

Organizations can setup their own SSI Web Wallet based on a shared [multi-tenant] Aries agent or on-prem [dedicated] Aries agent. For multi-tenant agent, platform handles all the processes. For dedicated agent, platform supports on-prem agent.

Multi-ledger & Multi-network Support

Our SSI SDK supports multi-ledger functionality, allowing you to interact with and utilize more than one blockchain or distributed ledger, including Indy and Polygon. Cheqd support is coming soon.

Additionally, it offers multi-network capabilities, enabling operations on different Indy networks, such as Sovrin, Indicio, and BCovrin and Polygon TestNet, MainNet.

Credential Schemas

A credential schema serves as a machine-readable template outlining a collection of attributes, data types and formats. These attributes are utilized for the claims within a credential. For instance, envision a schema tailored for generating passport credentials. It would encompass definitions of attributes like given name, family name, date of birth, passport number, and more. The versatility of a schema definition allows multiple credential issuers to utilize it, promoting standardization across various issuers.

Credential Definition

Once a schema has been authored and added to the ledger, it becomes accessible for use by a diverse range of credential issuers, such as banks, passport offices, universities, employers, and more. These issuers can then formulate issuer-specific credential definitions, which are also registered on the ledger. Each of these credential definitions constitutes an instance of the underlying schema, supplemented by attribute-specific public verification keys that are securely linked to the corresponding private signing keys of the respective issuer. This approach enables an issuer to re-use an existing schema, and enables a verifier who receives a proof containing data from the issuer to look up the issuer’s credential definition on ledger, obtain their verification key(s) and verify the origin and integrity of that data.

Verifiable credentials (VCs) have these qualities:

  • Portability: You can easily send them to others online.

  • Verifiability: You can check who issued the credential, who holds it, if it’s unchanged, and if it’s valid.

  • Privacy: You can choose what info to share using zero-knowledge proofs, giving you more control.Integrity: VCs can’t be changed or faked.”

Verification credential Stake-holders:

  • Issuer: The entity that generates the Verifiable Credential and provides it to another entity.

  • Holder: The entity that possesses the verifiable credential in their digital wallet.

  • Verifier: The entity that gets and verifies instantly the shared information.

Credential Lifecycle Management

Issuance, Verification & Revocation

The platform provides a consistent process for creating and managing the VC lifecycle. It empowers the trusted issuers (like Universities, Employers, or Government Agencies) to seamlessly issue or revoke digital credentials to individuals.

Furthermore, the platform furnishes a means for individuals or entities relying on the credentials to cryptographically verify and confirm the legitimacy of the credential provided by individuals. These entities are typically Employers, Educational Institutions, or any other entity requiring validation of someone’s qualifications or other identity claims.

ADEYA Mobile SDK features

ADEYA Mobile SDK enables developers to build a mobile app for holders to store credentials and present proof to verifiers:

Privacy & User Control

Designed with user's data privacy and control in mind to securely store and share verifiable credentials.

Multiple DID methods & VC formats

Support multiple DID methods, including did:indy, did:polygon, did:web, did:key ensuring flexibility across various decentralized identity systems.

Support storage of multiple VC formats, such as AnonCreds and W3C JSON-LD, ensuring broader compatibility.

Backup and Restore

Regularly backup wallets on your preferred storage location and restore as needed

Interoperable

Interoperable with other wallets and SSI providers/platforms that follow open standards

Last updated