did:abt

ABT DID Method is a blockchain-based decentralized identifier implementation developed by ArcBlock that focuses on enhanced privacy and security. The method implements the W3C DID specification while adding unique features for privacy protection and key management.

The method's core innovation is its approach to privacy-preserving identity management through the use of extended DIDs - where users generate separate DIDs for each application interaction while maintaining a single master DID that is never exposed publicly. This reduces correlation risks across different services.

The system operates on ArcBlock's blockchain infrastructure and utilizes ED25519 cryptography for digital signatures. Unlike some other DID methods, did:abt requires explicit DID declaration on-chain through transactions before a DID becomes visible to others.

Key capabilities include:

• Hierarchical Deterministic (HD) key derivation for managing multiple DIDs
• Zero-knowledge proofs for selective disclosure
• Built-in verifiable claims system
• Multi-party authentication protocol
• Integration with blockchain-based trust registry

Technical Details:

1. DID Generation and Structure:

• DIDs follow format: did:abt:<base58-string>
• Generated through multi-step process:
  • Combines RoleType, KeyType, and Hash parameters
  • Uses SHA3 hashing
  • Applies Base58 encoding
  • Includes checksum for integrity

2. Resolution Process:

• Utilizes GRPC requests to network
• Supports historical state queries through height parameter
• Returns complete DID Document as account state

3. Key Management:

• Implements HD wallet architecture
• Supports multiple key types including ED25519 and secp256k1
• Uses role-based access control
• Features built-in key rotation capabilities

4. Security Features:

• Replay attack prevention
• Man-in-the-middle protection
• Message integrity verification
• Authentication mechanisms for all operations

5. Technology Stack:

• Built on ArcBlock blockchain platform
• Uses JWT for authentication tokens
• Implements GRPC for communication
• Supports IPFS for document storage
• Utilizes SHA3 and ED25519 cryptography