did:myDiD

myDID is a decentralized identifier method built for EVM-compatible blockchains that enables individuals and organizations to create and manage their digital identities. The method leverages the security and decentralization properties of Ethereum Virtual Machine networks while maintaining compatibility with W3C DID standards.

The method implements a hybrid approach to DID Document storage, utilizing both on-chain and off-chain components. DID Documents are stored directly on the blockchain through a smart contract for essential data (like controllers and primary public keys), while additional data can be maintained off-chain. This dual-storage approach helps balance costs and scalability.

Each myDID identifier is structured using a base58-encoded format derived from an Ethereum public key, making identifiers human-readable while preserving the cryptographic properties. The method supports core DID operations including creation, updating, and revocation of identifiers.

Key features include:

• Blockchain-based security and immutability
• Hybrid storage architecture
• Smart contract based management
• Full compatibility with W3C DID standards
• Off-chain resolution capabilities

Technical Details:

1. DID Generation and Structure:

• Format: did:mydid:<base58EncodedPublicKey>
• Generated from Ethereum address derived from public key
• Uses base58 encoding for human readability
• Example: did:mydid:zr389Hiajsikam23jdsFK38FJ28dsj

2. Resolution Process:

3. Extract Ethereum address from identifier

4. Query smart contract for on-chain DID Document

5. Retrieve off-chain DID Document if referenced

6. Merge and return combined DID Document

7. Key Management and Security:

• Uses EcdsaSecp256k1VerificationKey2019 for authentication
• Implements EcdsaSecp256k1RecoveryMethod2020 for assertions
• Transaction signing required for all updates
• Nonce-based replay attack prevention
• Controller-based access control

4. Unique Characteristics:

• Dual Document architecture:
  • On-chain for essential data
  • Off-chain for extended information
• Smart contract based management
• IPFS integration for service endpoints
• Revocation mechanism through status updates

5. Technology Stack:

• Primary Components:
  • Solidity smart contracts
  • NodeJS reference resolver
  • React web application
• Infrastructure:
  • EVM-compatible blockchain
  • IPFS for off-chain storage
  • Web3 interfaces for blockchain interaction

Security Considerations:

• Immutable transaction history
• Public key cryptography for authentication
• Rate limiting for DoS protection
• Blockchain-inherent security properties