did:health

The DID:HEALTH method is a decentralized identifier system built on Ethereum that enables any Ethereum address, smart contract, or secp256k1 public key to become a valid identifier without requiring explicit registration. Based on the ERC1056 standard, it provides a lightweight identity management system designed for off-chain usage while leveraging Ethereum's infrastructure.

The method supports key management and service endpoints through smart contracts deployed on various Ethereum networks, including Mainnet, Ropsten, Rinkeby, and Kovan. A key feature is its support for meta-transactions, allowing third parties to fund transaction fees without changes to Ethereum's architecture.

Key advantages include:

• Zero-cost identifier creation
• Private identifier generation
• Multi-signature wallet support
• Flexible key management
• Third-party transaction funding
• Cross-chain compatibility with any EVM-compliant blockchain
• Verifiable versioning

The method separates the identity data from the underlying identifier and utilizes Ethereum's native account abstraction, making it highly flexible for various identity management scenarios.

Technical Implementation:

1. DID Generation and Structure

• Format: did:health:<ethereum-address or public-key-hex>
• Optional network prefix: did:health:<network>:<identifier>
• Supports both Ethereum addresses (40 hex chars) and secp256k1 public keys (66 hex chars)
• Uses ERC1056 contract for identity management

2. Resolution Process

• Resolves through read-only functions on the ERC1056 registry
• Builds DID document by processing three event types:
  • DIDOwnerChanged
  • DIDDelegateChanged
  • DIDAttributeChanged
• Supports versioned resolution through versionId parameter

3. Key Management Features

• Controller Address system for identity ownership
• Delegate Keys for signing and authentication
• Supports multiple key types:
  • Secp256k1
  • RSA
  • Ed25519
  • X25519

4. Security Model

• One-to-one mapping between Ethereum addresses and DIDs
• Versioning security considerations for compromised keys
• No PII in DID documents
• Supports key revocation and document deactivation

5. Technology Stack

• Built on Ethereum blockchain
• Uses ERC1056 smart contracts
• Implements W3C DID specification
• Supports JSON-LD context
• Compatible with CAIP10 blockchain account format