did:ccp

The did:ccp method is a blockchain-based digital identity system developed by Baidu that implements the W3C DID specification. This method operates on a permissioned blockchain network derived from Quorum, offering enhanced privacy features and node admission controls.

The method is designed to provide decentralized digital identities for both enterprises and individuals, with a focus on maintaining complete control over identity data. Key use cases include financial KYC, unified membership systems, digital identity management, and IoT device identity.

The system employs a dual-key architecture with both primary and recovery keys, enhancing security and providing backup mechanisms. All private user data is stored off-chain with authorized issuers, while the blockchain only maintains the DID Documents and public verification information. The method supports both Secp256k1 and RSA cryptographic algorithms.

Notable features include:

• HD Wallet compatibility following BIP-32 and BIP-39 standards
• Challenge-response authentication mechanism
• Version control for DID Documents
• Service endpoint management
• Privacy-preserving architecture with off-chain personal data storage

Technical Implementation:

1. DID Generation and Structure:

• Format: did:ccp:<method-specific-id>
• ID Generation: base58(ripemd160(sha256(<Base DID Document>)))
• Supports both Secp256k1 and RSA key types
• Implements dual-key architecture:
  • Primary key for authentication
  • Recovery key for backup/restoration

2. Resolution Process:

• Utilizes dedicated DID Resolver endpoints
• Supports version-specific resolution via paths (/<version>)
• Returns complete DID Documents with:
  • Public keys
  • Authentication methods
  • Service endpoints
  • Proof signatures

3. Key Management:

• Primary Keys for regular authentication
• Recovery Keys for key rotation and DID recovery
• Signatures follow ASN.1 DER Encoding format
• Support for BIP-32/BIP-39 HD wallet integration

4. Security Features:

• Challenge-response authentication protocol
• Document versioning system
• Proof signatures for document integrity
• Off-chain privacy data storage
• Permissioned blockchain infrastructure

5. Technology Stack:

• Built on Quorum-based blockchain
• Uses base58 encoding
• Implements ripemd160 and sha256 hashing
• Supports Secp256k1 cryptography
• RESTful API endpoints for resolution