did:hid

The did:hid method is a decentralized identifier specification built on the Hypersign Identity Network, a permissionless blockchain network designed for digital identity management. This method enables self-sovereign identity implementation while maintaining compatibility with W3C DID specifications.

The method supports two distinct approaches for identifier generation:

• CAIP-10 Blockchain Account IDs for direct wallet address linking
• Alphanumeric IDs for flexible identifier formats like UUIDs or domain names

Built using the Cosmos SDK, the network facilitates cross-chain identity verification through the Inter-Blockchain Communication (IBC) Protocol. Key use cases include web3 reputation systems, on-chain KYC, and organizational identity management.

The method implements a robust security model through:

• Multi-controller support allowing shared control of DIDs
• Flexible key management supporting multiple verification methods
• Blockchain-based persistence ensuring immutable identity records
• Signature-based operations for all identity management functions

1. DID Generation and Structure:

• Format: did:hid:[chain-namespace]:<method-specific-id>
• Supports two identifier types:
  • CAIP-10 blockchain account IDs
  • Custom alphanumeric identifiers
• Optional chain-namespace parameter for network specification

2. Resolution Process:

• Direct query through gRPC or API endpoints
• Returns full DID document with metadata
• Includes version tracking and deactivation status
• Supports grpc-gateway integration

3. Key Management Features:

• Supports multiple verification method types:
  • Ed25519VerificationKey2020
  • EcdsaSecp256k1VerificationKey2019
  • EcdsaSecp256k1RecoveryMethod2020
• ClientSpec support for wallet-specific signature verification
• Flexible controller management

4. Unique Characteristics:

• Native support for popular blockchain wallets like Keplr and MetaMask
• Cross-chain identity verification through IBC
• Dual identifier format support
• Version control system for DID documents

5. Technology Stack:

• Built on Cosmos SDK
• Uses grpc-gateway for API access
• Implements W3C DID specifications
• Supports multiple signature verification protocols
• Blockchain-based verifiable data registry