did:ens

The did:ens method integrates the Ethereum Name Service (ENS) with Decentralized Identifiers by wrapping existing ENS names as DIDs. Built on the Ethereum blockchain, this method leverages the established ENS infrastructure, which provides human-readable names (like 'example.eth') that map to machine-readable identifiers such as Ethereum addresses and content hashes.

The method enables existing ENS names to become fully-functional DIDs while maintaining their original capabilities. It operates primarily on the Ethereum mainnet but supports multiple networks including test networks like Rinkeby and Ropsten. The hierarchical nature of ENS allows domain owners to create and configure subdomains, providing flexible identity management.

Key features include:

• Automatic verification method generation from ENS ownership
• Web3 public profile integration
• Support for custom service endpoints
• Hierarchical naming structure
• Cross-network compatibility

The method adds DID capabilities to ENS names through TEXT records, allowing the addition of service endpoints and verification methods while maintaining backward compatibility with existing ENS infrastructure.

DID Generation and Structure

1. Format: did:ens[:<network>]:<name>

   • Network parameter is optional (defaults to mainnet)
   • Name must be a valid ENS name
   • Names undergo UTS-46 normalization

2. Examples:

   did:ens:example.eth
did:ens:mainnet:example.eth
did:ens:sub.example.eth

Resolution Process

The resolution involves:

• ENS name resolution on the blockchain
• Retrieval of DID-specific TEXT records
• Generation of default verification methods and services
• Integration of custom verification methods and services

Key components:

• org.w3c.did.service
• org.w3c.did.verificationMethod
• org.w3c.did.verificationRelationship

Key Management and Security

Security Features:

• Uses ECDSA secp256k1 recovery for default verification
• Supports multiple verification relationships
• Integrates with Ethereum account security

Key Considerations:

• ENS names are transferrable NFTs
• Owner changes affect authoritative keys
• Privacy implications of human-readable identifiers

Technology Stack

Built on:

• Ethereum blockchain
• ENS infrastructure
• EIP-155 account identification
• CAIP-10 blockchain account IDs
• UTS-46 normalization

Supported verification method types:

• EcdsaSecp256k1RecoveryMethod2020
• X25519KeyAgreementKey2019