did:oyd

OwnYourData DID Method (did:oyd) is a lightweight approach to decentralized identifiers that does not rely on blockchain technology. Instead of using distributed ledgers, it maintains DIDs and DID Documents on one or more local or public storage locations while preserving security through cryptographic linking.

The method uses a directed acyclic graph (DAG) structure to maintain the provenance and state of DIDs through a series of cryptographically linked log entries. This enables verification of authenticity and ownership without requiring consensus mechanisms.

Key characteristics:

• Blockchain-free: Operates without distributed ledger technology
• Flexible Storage: Can use local files or HTTP endpoints to store DIDs
• Cryptographic Linking: Uses hash chains to verify document authenticity
• Multi-location Support: Allows cloning DIDs across multiple repositories for availability
• Key Rotation: Built-in support for key updates and revocation

Technical components:

• DID Format: did:oyd:<multibase-encoded-identifier>
• Storage Options:
  • Local file system
  • HTTP repositories
  • Multiple clone locations for redundancy
• Verification Process:
  • Hash verification of documents
  • Signature validation
  • Log record retrieval and validation

Primary use cases:

• Testing environments requiring many DIDs
• Offline or air-gapped systems
• Local networks with limited participants
• Temporary or transient storage solutions

Technical Details:

1. DID Generation and Structure

• DIDs are generated using MULTIBASE and MULTIHASH encodings
• Format: did:oyd:<base58btc-encoded-multihash>
• Default hash algorithm: SHA2-256
• Includes payload, keys, and log references

2. Resolution Process

1. Query repository for DID document
2. Verify hash linkage to identifier
3. Check log entries for updates/revocations
4. Validate signatures and ownership chain

3. Key Management

• Uses ED25519 key pairs by default
• Separate keys for document signing and revocation
• Supports key rotation through update operations
• Cryptographic agility through MULTICODEC support

4. Security Features

• Hash-based document integrity
• Signature-based ownership verification
• Revocation support
• Clone-based availability

5. Technology Stack

• MULTIBASE encoding
• MULTIHASH for cryptographic digests
• MULTICODEC for key formats
• JSON for document format
• HTTP APIs for remote storage

The method is implemented through:

• Command-line tool (oydid)
• Repository server implementation
• Universal Resolver driver
• JavaScript resolver library