did:pkh

The did:pkh method is a decentralized identifier solution designed to wrap existing blockchain addresses into standard W3C DID format. This method enables the hundreds of billions of existing blockchain accounts across major networks to function as DIDs without requiring additional on-chain transactions or infrastructure.

The method works by taking a blockchain account's public key hash (PKH) and wrapping it in a DID format that follows the CAIP-10 standard for blockchain account identification. It supports multiple blockchain networks including Ethereum, Bitcoin, Solana, Tezos, Celo, and others.

Key features include:

• Instant DID creation from existing blockchain addresses
• Multi-chain support across major blockchain networks
• Zero additional infrastructure requirements
• Compatibility with W3C Verifiable Credentials
• Integration with blockchain wallets for authentication

Unlike other DID methods, did:pkh is deliberately minimal and unopinionated, focusing on providing basic DID functionality for existing blockchain accounts. It does not support key rotation or DID document updates, making it similar to did:key in being stateless and purely generative.

Technical Implementation:

1. DID Generation

• Format: did:pkh:<CAIP-10-address>
• Example: did:pkh:eip155:1:0xb9c5714089478a327f09197987f16f9e5d936e8a
• Validates addresses using CAIP-10 standard before generation

2. Resolution Process

• Parses DID into network ID and account address
• Generates JSON-LD DID document with:
  • Standard W3C DID context
  • Verification methods based on network type
  • Authentication and assertion capabilities

3. Security Features

• Address validation using CAIP-10
• Network-specific verification method types
• Blockchain-native signing capabilities

4. Technology Stack

• Built on CAIP standards for chain identification
• Supports multiple cryptographic suites:
  • EcdsaSecp256k1RecoveryMethod2020
  • Ed25519VerificationKey2018
  • Ed25519PublicKeyBLAKE2BDigestSize20Base58CheckEncoded2021

5. Unique Characteristics

• No on-chain components required
• Deterministic generation from existing addresses
• Cross-chain compatibility
• Upgrade paths to other DID methods