did:monid

MONiD is a decentralized identifier method that combines Ethereum blockchain and the Interplanetary File System (IPFS) to create a robust digital identity solution. The method uses did:monid as its prefix and leverages IPFS as its primary verifiable data registry for storing DID Documents, while utilizing Ethereum for maintaining a registry of mappings between DIDs and their corresponding IPFS addresses.

A key distinguishing feature of MONiD is its integration with the Torus Network for key management. This provides users with a more accessible experience through social authentication while maintaining security through distributed key sharing across the network. The system splits private keys into shares across Torus nodes, offering both security and recoverability.

The architecture consists of several core components:

• A RESTful API server for DID operations
• A DID resolver compatible with W3C DID specifications
• A registry module for IPFS document management
• An Ethereum smart contract for DID-to-IPFS mapping

MONiD creates DIDs by:

1. Retrieving user public keys from Torus Network
2. Computing the keccak256 hash of the public key
3. Generating the DID in the format did:monid:<public-key-hash>

The system stores DID Documents on IPFS, making them immutable once published. This provides a strong security guarantee as documents cannot be altered without controlling the private key that registered them. The method supports standard DID operations including creation, resolution, updating, and deactivation through its smart contract interface.

Technical Specifications:

1. DID Generation and Structure:

• Format follows did:monid:<keccak256-hash-of-public-key>
• Implements the W3C DID Core specification
• Uses Secp256k1 keys for cryptographic operations

2. Resolution Process:

• Queries Ethereum smart contract using getRecord function
• Retrieves IPFS hash associated with DID
• Resolves IPFS address through MONiD IPFS Gateway
• Returns complete DID Document

3. Key Management and Security:

• Integrated with Torus Network for key management
• Implements distributed key sharing
• Supports social authentication
• Features managed volumes and snapshot policies for key recovery

4. Technology Stack:

• @monid/did-driver: RESTful API implementation
• @monid/did-resolver: DID resolution module
• @monid/did-registry: IPFS integration module
• @monid/registry-contract: Ethereum smart contract wrapper

5. Document Structure:

{
  "@context": "https://w3id.org/did/v1",
  "id": "did:monid:<identifier>",
  "publicKey": [...],
  "service": [
    {
      "type": "MONiDPublicProfile",
      "serviceEndpoint": "https://ipfs.monid.io/<hash>"
    }
  ]
}