did:web, did:key and did:polygon.✅ Fulfils Criteria
🟠 Dependency / Questionable
❌ Does not fulfil criteria
❓ Unclear
| Website | https://credebl.id |
|---|---|
| Solution source | https://github.com/credebl |
| Developed in | India |
| Deployed in | India |
| OSS Insight | https://next.ossinsight.io/analyze/credebl?period=past_90_days#overview |
Credebl is a product of Blockster labs (Adeya wallet is also a product) and is owned by parent company Ayanworks Technological Solutions Private Limited (both companies have the same CEO and CTO). Credebl and Adeya are protected by intellectual property rights and are owned and licensed by Blockster labs.
| Evaluation | Details |
|---|---|
| People | Kalayan Kulkarni |
| Ajay Jadhav | |
| Ownership | Privately Held (Blockster labs) |
| Company | Ayan Works Technological Solutions Private Limited - Through Blockster labs |
| Team Size | 1-10 |
| Founded | 2019 (Blockster labs) |
| Funding | Unfunded? |
| Revenue | $727k (ayanworks) 2022 |
| Project Status | Active |
| Last Commit | 3 months ago ‣ |
| last week ‣ | |
| Integrations | Cheqd, Polygon, Indy Ledgers, Sovrin, Indicio, Credo |
| Associated Products | ‣ |
| https://github.com/ayanworks | |
| API | 🟠 Yes but no documentation |
| SDK | ❌ |
| Credential Management | Are there means for credential management? Yes ✅ |
| Regulatory Compliance | Are there mechanisms in place for ensuring ongoing compliance with changing regulatory requirements? |
| 🟠 Unclear |
| High-Level Criteria | Sub Goals | Description | Credebl | Source |
|---|---|---|---|---|
| Foundational Property | Existence | A self-sovereign identity must enable a user to encode her characteristics digitally. | ✅ Credebl supports digital encoding of user characteristics through DIDs and VCs | https://docs.credebl.id/en/intro/intro-to-ssi/ |
| Autonomy | The model leverages decentralized domains where no singly party can assert its control. This enables a user to create/manage as many self-sovereign partial identities as required without relying on a specific provider | 🟠 Functions are managed by a SSI wallet (organisations may integrate their own wallet, Adeya, a wallet created by the same company is also available) | https://docs.credebl.id/en/guides/architecture/ | |
| Ownership | Only the creator of the identity can claim ownership. Model enforces that assertions from the providers are released only by the owner. | 🟠 Organisations can setup their own SSI Web Wallet based on a multi-tenant shared Aries agent. | https://docs.credebl.id/en/guides/architecture/ | |
| Access | Users must have unrestricted access to their identity information. | 🟠User registration process through email-based verification. FIDO Passkey for phishing-resistent user verification. | https://docs.credebl.id/en/guides/architecture/ | |
| Single Source | If any provider-asserted claim is only released via a profile leveraged by a self-sovereign identity as advocated previously, the user can act as the single source of truth regarding her identity. | ✅ inherited from the protocol and the trust assumptions on the credential | https://docs.credebl.id/en/guides/architecture/ | |
| Security Property | Protection | Well-protected with the latest cryptographic mechanisms. | ✅ (See technical evaluation below) | |
| Availability | Any identity data in a decentralized domain will be readily available and accessible as long as such domain exists. | 🟠Ledger agnostic. Dependent on liveness of ledger used/ chain deployment . (see below on decentraliazation) | https://docs.credebl.id/en/guides/architecture/ | |
| Persistence | Data in a decentralized domain will be persistent as long as the domain exists. | 🟠Ledger agnostic. Dependent on the ledger used/ chain deployment . (see below on decentralization) | https://docs.credebl.id/en/guides/architecture/ | |
| Controllability Property | Choosability | User control over when and to whom identity data is released. | 🟠 Supports selective disclosure features | https://docs.credebl.id/en/intro/platform-features/ |
| Disclosure | Ability to selectively disclose attributes. | ✅ Supports selective disclosure features (but NOT bbs+ and nothing on the roadmap) unsure if uses zkps | ||
| Consent | Data released to third parties only with user consent. | ✅ See data privacy in table below | https://app.digitalpublicgoods.net/a/10902 | |
| Flexibility Property | Portability | Identity data must be portable across different platforms. | ✅ Uses VCs and adheres to various standards (see below) | https://app.digitalpublicgoods.net/a/10902 |
| Interoperability | Designed for maximum interoperability with other systems. | ✅ .Designed for interoperability with W3C specifications such as Decentralized Identifiers (DID) and Verifiable Credentials (VC), along with contributions from the Decentralized Identity Foundation (DIF), Trust over IP Foundation (ToIP), as well as the collaborative efforts of the Hyperledger Indy and Aries open-source initiatives. | https://docs.credebl.id/en/intro/what-is-credebl/ | |
| Minimisation | Minimize disclosure of identity data. | ✅ Agent creates a separate wallet database for each organization wallet in order to keep the data isolated. Platform uses NATS for message-driven data exchange between CREDEBL microservices. | https://docs.credebl.id/en/guides/nats/ | |
| Sustainability Property | Transparency | The system must be transparent to all involved entities. | ✅ Credebl is open-source | https://app.digitalpublicgoods.net/a/10902 |
| Standard | Based on open standards for maximum portability, interoperability, and adoption. | ✅ Based on open standards DID, VC, DIF, ToIP, W3C* see above | https://app.digitalpublicgoods.net/a/10902 |
| --- | --- | --- | --- |
| --- | --- | --- | --- |
| On-chain Deployment Requirements | Requirements for deploying the solution on-chain. | Signatures verification
If using BBS+, depending on the curve implemented, it should be possible to implement the verification logic for the EVM, though I didn’t see any on-chain verifier at the moment, could lead to research and implementation on our side.
For CL signatures it should also be possible but again no verifier implementation found for the EVM.
Data storage The protocol is currently using Polygon PoS, to post unique user identifiers (DID identifiers) in a decentralised registry, as well as the schemas for VCs (optional). | https://github.com/hyperledger/anoncreds-clsignatures-rs |
For most updated Dashboard For Credebel: https://next.ossinsight.io/analyze/credebl#overview
Dashboard for Ayan Works: https://next.ossinsight.io/analyze/ayanworks?repoIds=725101845&period=past_12_months#engagement
| --- | --- | --- |