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