chevron-icon
Active RFP

Decentralized Digital Identity (DDI) Research

Top
chevron-icon
Juana Attieh
RFP Owner

Decentralized Digital Identity (DDI) Research

Research on a decentralized digital identity (DDI) hub to integrate existing decentralized identity solutions to ensure unique verifiable identities for reputation scores

  • Type Community RFP
  • Total RFP Funding $120,000 USD
  • Proposals 0
  • Awarded Projects n/a

Overview

  • Est. Complexity

    💪 80/ 100

  • Est. Execution Time

    ⏱️ 3 Months

  • Proposal Winners

    🏆 Single

  • Max Funding / Proposal

    $120,000USD

RFP Details

Short summary

The goal of this project is to conduct research on solutions and requirements for a decentralized digital identity (DDI) hub tailored to the needs of the SingularityNET ecosystem and its reputation system. This will include research into how existing DDI solutions can be integrated into a single hub that will allow for the creation of reputation scores that can be tied to unique verifiable identities while maintaining privacy. Part of the RFP is the definition of 2 or 3 RFPs for development of the envisioned system. This RFP is closely connected to the Reputation Platform RFP, and should be guiding the data privacy and identity integration solution of that RFP. 

Long description

The outcome of this research RFP should include insights, recommendations, and solutions consolidated into an RFP for development for the following:

  • Consideration of existing applicable DDI solutions, their methods, solutions, and integration feasibility (e.g., Gitcoin Passport, Privado, Identus, etc.).
  • Explore expanding WaLT (Wallet Linking Tool) into the potential DDI Hub, leveraging its ability to consolidate wallet addresses into a single user ID and examining how it could integrate additional identity systems.
  • Define how the DDI Hub will integrate with existing components in the SingularityNET ecosystem, such as the Voting Portal, WaLT, and Deep Funding portals. 
  • Investigate concepts for generating sub-IDs tied to specific sources (e.g. the Deep Funding portal and Social Media channels) and events (e.g. a voting event) to manage data access for approved privacy-preserving integrations.
  • Investigate options to share data with the SNET Reputation System and calculate outcomes in a privacy preserving way, as proposed in this document 
  • Consideration of existing Decentralized Identity schemes, standards, and technical solutions. Suitability analysis of existing building blocks around decentralized identifiers (e.g. DDI methods), credentials formats (e.g. W3C verifiable credentials), communication/exchange protocols (e.g. OpenID4VC suite) and governance frameworks.
  • Develop mechanisms to ensure that a single individual cannot present multiple identities within the system, especially for high-stakes use cases like voting or funding processes.
  • Requirements for a hub that can integrate multiple DDI systems under a single framework while maintaining privacy and preventing identity duplication
  • Approaches to verifying identity with tools such as face recognition without compromising privacy and allowing for private storage of this data and information
  • Research and evaluate the potential for integrating KYC frameworks currently being explored within the Deep Funding initiative. This includes Zero-Knowledge Proof (ZKP) KYC solutions like Hakata.io, fractal.io, etc., and potentially self-hosted KYC systems or a combination of both. The research should remain flexible to incorporate new findings as they become available.
  • Details on research methodology, data collection, analysis techniques, and findings
  • Outline integration and data-sharing protocols with external ecosystem components, including APIs, endpoints, data formats, and lifecycle management.
  • 2-3 RFPs as outcome determining next steps for development. These RFPs should cover the full architecture for an end to end ZKP reputation and identity system. 
    • DDI Hub with a selection of expected integrated ID systems and architecture
    • WaLT, including sub-ID generation, DDI integration, perhaps some way to connect an ID to a social media platform and a ZKP integration with the Reputation platform
    • Specification of architecture and integration details of the current Reputation Platform RFP, including a clear solution direction for Identity Integration and Privacy & Data Protection. NB: We expect this part to be prioritized to support the team working on the Reputation Platform. 
  • Close collaboration with the team working on the Reputation Platform 

Functional Requirements

Must have:

  • Identification of requirements for a DDI hub capable of integrating existing DDI solutions
  • Identification and consideration of existing DDI solutions and unique aspects of these that need to be accounted for if integrating identities (e.g., Gitcoin Passport, Privado, open passport, Identus, WaLT, etc.)
  • Exploration of expanding WaLT as the foundation for the DDI hub. Utilize WaLT to aggregate wallet addresses into a single user ID. Expand its capability to associate additional identity attributes from other DDI systems.
  • Identification of methods that can be used to ensure identities are tied to unique verifiable individuals to prevent the use of multiple identities for a single user.
  • Explore how the outputs of microservices of the reputation system can be mapped to a single unique identifier (UID) managed and outputted by the DDI Hub.
  • Methods to allow self-sovereign control of identity. 
  • Evaluate optimal Zero-Knowledge Proof (ZKP) KYC solutions as a target. Consider the distinction between SaaS and on-premise solutions as a study object.
  • Define Integration and Data Sharing Protocols:
  • Specify what data and identity-related information will be shared with the DDI Hub by other ecosystem components (e.g., voting portal, blockchain explorer).
  • Define clear guidelines for external services integrating with the DDI Hub, including:
  • APIs and endpoints for accessing identity verification and metadata.
  • Data formats and protocols for interoperability
  • Access control and permissions to ensure only authorized components can query identity data.
  • Include mechanisms to anonymize or pseudonymize data shared with other services to maintain user privacy.
  • Outline the data lifecycle within the DDI Hub, including how data is stored, processed, and deleted to comply with privacy and security standards. How identity verification requests are initiated, processed, and terminated. Procedures for revoking identities in case of breaches or user withdrawal.
    • Details on research methodology, data collection, analysis techniques, and findings
  • Evaluate the integration of KYC frameworks and existing decentralized identity and KYC solutions. Consider the distinction between SaaS and on-premise solutions as a study object.
  • Security considerations for protecting against vulnerabilities in the DDI Hub.
  • Incorporation of Legal and Compliance Best Practices:
    • Research and recommend approaches for compliance with relevant legal frameworks (e.g., GDPR, CCPA) to ensure privacy and data security.
  • Identify potential risks related to data handling, user privacy, and identity management.

Should Have:

  • Requirements for a modular architecture that can enable the integration of future DDI solutions that may be developed
  • Identification of standards that can be leveraged to integrate DDI solutions 
  • Consideration of existing solutions for DDI integration
  • Identification of methods to allow for private data storage with user control

Could Have:

  • Formulation of new standards or solutions that could be used to enable the integration of DDIs while providing guidance for how future DDIs should be built for interoperability
  • Recommendations for incorporating advanced features like reputation-based DDI weighting or concepts like soulbound tokens and community recovery mechanisms.
  • Description of an end to end, privacy preserving integration between the DDI hub, WaLT and the SNET Reputation System. (Possibly utilizing sub-IDs as suggested in this doc.) 
  • 3 RFPs outlining next steps for development

 

Non-functional Requirements

Directions on the expected architecture

  • Research should provide guidance on tools and architecture needed to allow for the integration of different DDI solutions into a single hub that can ensure unique verifiable identities while preventing duplication of identity and maintaining privacy

Specific integration requirements

  • Research should include information on technical aspects needed to ensure that existing DDI solutions would be able to integrate in a DDI hub

Security requirements

  • Identify best practices to address vulnerabilities like identity spoofing, unauthorized access, or KYC fraud.

Scalability

  • Research how the DDI Hub can scale to accommodate additional identity solutions.

Data quality

  • Teams should appropriately cite relevant sources and identify any data obtained and used as part of the research

Reliability

  • Research should be supported with appropriate references and citations to support the project and give confidence in the findings

General Modularity/composability/extensibility

  • Research should examine what would be requirements allowing the integration of future DDIs into a DDI hub without disrupting the functionality of an existing solution

Documentation

  • Appropriate references and citations, identification of research methodology, data collection techniques, data analysis techniques, integration strategies, technical recommendations and security, legal and compliance best practices

Main evaluation criteria

  • Alignment with requirements and objective: Does the proposal meet the requirements and advance the objectives of the RFP
  • Pre-existing R&D: Has the team previously done similar or related research work in other contexts
  • Team Competence: Does the team have relevant skills and research experience
  • Cost: Does the proposal offer good value for money
  • Timeline: Does the proposal include a set of clearly defined milestones

 

Other resources

There are existing resources on DDI integration and DDI standards that the awarded team may be able to leverage in responding to the RFP:

 

RFP Status

Submit Proposals for

Days
Hours
Minutes
Seconds
Ends: 3 Mar. 2025 12:00 UTC Submit Proposal
0 proposals

No Proposals Avaliable

Check back later by refreshing the page.

0 projects

No Projects Avaliable

Check back later by refreshing the page.

Join the Discussion (0)

feedback_icon