did:mydata

The did:mydata method is a specialized Decentralized Identifier system designed for managing Data Agreements between organizations and individuals. It provides a framework for tracking and managing personal data usage permissions in compliance with data protection regulations like GDPR.

This method enables three key capabilities:

• Data Agreement Signing between parties
• Authentication and Verification of agreement proof chains
• Transaction Association with specific data agreements

The method uses a DIDComm-based architecture and does not rely on any blockchain. Instead, it operates through an Automated Data Agreement (ADA) service that acts as a central registry. The system defines five distinct types of participants:

• Data Sources (organizations collecting data)
• Data Subjects (individuals)
• Data Using Services (organizations processing data)
• Assessors (who review practices and draft agreements)
• Auditors (who review compliance)

Each participant is assigned a unique identifier following the format did:mydata:<type>:<key> where type is a number (0-4) indicating their role. The method emphasizes privacy preservation by ensuring no personally identifiable information (PII) is stored in DID documents.

Technical Implementation:

1. DID Generation and Structure:

• Format: did:mydata:<type-integer>:<mb-value>
• Uses Ed25519 cryptographic keys
• mb-value is a base58-btc encoded Multibase value
• Type integers (0-4) identify participant roles

2. Resolution Process:

• Implements DIDComm protocol for all operations
• Uses JSON Web Encryption (JWE) for secure message exchange
• Resolution performed via read-did message type
• Supports both authenticated and anonymous resolution

3. Key Management Features:

• Based on Ed25519Signature2018 suite
• Implements anoncrypt and authcrypt modes
• Supports key rotation through delete/create operations
• No direct key update operations permitted

4. Core Technology Stack:

• DIDComm messaging protocol
• JSON-LD for DID documents
• Ed25519 cryptographic primitives
• HTTP transport with encryption envelopes

5. Unique Characteristics:

• Role-based DID typing system
• Data Agreement-centric architecture
• No blockchain dependency
• Integrated with GDPR compliance workflows
• Supports audit trails for data usage agreements