did:antelope

Antelope DID Method is a decentralized identifier specification designed to enable Self-Sovereign Identity capabilities for blockchains powered by the Antelope protocol. This method allows identities on Antelope-based chains to integrate with the broader SSI ecosystem while leveraging Antelope's unique account and permission structure.

The method supports both public and private Antelope blockchains through two DID identifier schemas:

• A registered chain name format (did:antelope:chainname:account)
• A chain ID format (did:antelope:chainid:account)

Key features include:

• Support for Antelope's hierarchical permission system
• Multi-signature capabilities
• Delegated authorization
• Compatibility with multiple key types including secp256k1 and secp256r1
• Integration with Antelope's native account structure

The method leverages Antelope's unique account abstraction where:

• Account names are human-readable (up to 13 characters)
• Accounts can have multiple public-private key pairs
• Keys are organized in a hierarchical permission tree
• Support for weighted multi-signature schemes

Technical Implementation:

1. DID Generation:

• DIDs are created through Antelope's native account creation process
• Uses the newaccount action on the system contract
• Format: did:antelope:{chain_id/registered_chain_name}:{account-name}

2. Resolution Process:

• Performed through Antelope blockchain API services
• Supports both public and permissioned access
• Resolves to a DID Document containing verification methods and services

3. Key Management:

• Supports multiple key types:
  • EOS_ (legacy)
  • PUB_K1_
  • PUB_R1_
  • PUB_WA_
• Uses ConditionalProof2022 verification type
• Implements hierarchical permission structures

4. Security Features:

• Transaction-based operations requiring authorized signatures
• Chain-specific replay protection
• Expiration times on transactions
• Support for delegated authority
• Multi-signature threshold schemes

5. Technology Stack:

• Built on Antelope blockchain protocol
• Uses WebAssembly
• Implements W3C DID Core specification
• Supports various API service types for resolution

The method is particularly notable for its integration with Antelope's sophisticated permission system while maintaining compliance with W3C DID standards.