LAC1 DID Method Specification

The LAC1 DID Method is a decentralized identifier specification that builds upon the ethr DID method while introducing enhanced capabilities for digital identity management. Developed by LACChain, this method enables precise encoding of DID registry paths and introduces innovative features for key management and revocation.

The method's distinguishing features include:

• Backwards revocation time support allowing controllers to specify historical revocation points
• Direct DID registry resolution from the identifier itself
• Flexible versioning system for backwards compatibility
• Transparent key management through blockchain-based logging

The specification follows the W3C DID Core standards while adding capabilities specifically valuable for enterprise and regulatory use cases where precise control over key validity periods is essential.

Technical Details

Purpose and Scope

• Primary identifier format: did:lac1:<base58-specific-identifier>
• Supports both Externally Owned Accounts and Contract Accounts on EVM-compatible networks
• Designed for transparent and auditable identity management

Key Technical Specifications

1. Identifier Structure:

   • did-version-bytes (2 bytes)
   • did-type-bytes (2 bytes)
   • data-buffer-bytes (variable length)
   • Checksum validation

2. DID Document Components:

   • Verification Methods
   • Service Endpoints
   • Delegate Keys
   • Controller Address

Implementation Requirements

1. CRUD Operations:

   Create: Off-chain generation
   Read: Event-based document construction
   Update: Smart contract function calls
   Delete: Controller address set to 0x0
   

2. Event Types:

   • DIDAttributeChanged
   • DIDDelegateChanged

Security Considerations

• Versioning Security:
  • Careful handling of versioned DID URIs required
  • Timestamp verification recommended for versioned DIDs
  • Clear user notification for potentially revoked data

Interoperability Features

• Supports query parameters:
  • versionId
  • versionTime
  • forTime
• Compatible with CAIP10 blockchain account identifiers
• Follows W3C DID Core specifications

Current Adoption Status

Implementation status marked as TBD (To Be Determined) in the specification

The method is designed for use within the LACChain ecosystem but can be implemented on any EVM-compatible network.