did:vivid

Vivid DID is a platform-agnostic Self-Sovereign Identity solution designed to work across multiple blockchain platforms. The method enables identity management through a flexible architecture that supports multiple verification methods and blockchain networks simultaneously. Unlike blockchain-specific DID methods, did:vivid operates across different distributed ledger platforms including NEO and Zilliqa.

The method's core feature is its ability to maintain multiple authentication methods for a single identity across different blockchain platforms. Each DID Document can contain multiple verification methods using different cryptographic algorithms (secp256r1 and secp256k1) tied to different blockchain networks. This multi-platform approach allows for greater flexibility and interoperability in identity management.

Key characteristics include:

• Platform agnostic design allowing integration with multiple blockchains
• Mandatory verification method that cannot be removed
• Support for multiple cryptographic suites
• Base58 encoded identifiers
• No storage of Personally-Identifiable Information (PII)

The method implements standard CRUD operations through smart contracts deployed on supported blockchain platforms, accessible via the Asteroid SDK. All DID document states are permanently stored on the underlying distributed ledgers, making historical states always accessible.

Technical Implementation:

1. DID Generation and Structure

• Format: did:vivid:<subnamespace>:<namestring>
• Namestring requirements:
  • 16-128 characters long
  • Uses Base58 character set
  • Generated using standard UUID methods
  • Example: did:vivid:znWRVY1GSUSjJEFqD8hRBc6s68qkQ9MGsaSRNZc8ZaMX

2. Resolution Process

• Implemented through ReadIdentity function
• Returns complete DID Document with:
  • Multiple verification methods
  • Authentication references
  • Key agreement capabilities
  • Issuance timestamp

3. Key Management and Security

• Supports multiple verification methods:
  • secp256r1 for NEO platforms
  • secp256k1 for Zilliqa
• Authentication through any registered verification method
• Mandatory initial verification method cannot be deleted
• No PII storage allowed in DID documents

4. Unique Characteristics

• Cross-platform verification methods
• Immutable history of all document states
• Smart contract based implementation
• Platform-specific cryptographic algorithms

5. Technology Stack

• Asteroid SDK for integration
• Multiple blockchain platforms:
  • NEO 2.0
  • NEO 3.0
  • Zilliqa
• Smart contracts with common interface
• Base58 encoding for identifiers
• Standard W3C DID specification compliance