Aurigraph's DID Ledger implements a W3C DID Core v1.0 compliant decentralized identity registry backed by a persistent Merkle tree with ML-DSA-87 (FIPS 204, formerly CRYSTALS-Dilithium) root signatures. Every DID document is versioned, anchored, and independently verifiable — with portable proof export in JSON-LD and JWT formats and cross-chain bridge support for Ethereum and Solana.
Traditional:
DID stored in single database row | (No cryptographic anchoring) Resolution = simple key-value lookup | (No tamper evidence, no versioning) Proof requires trust in the registry operator
Aurigraph:
DID Document (did:aurigraph:5Hq3...) | (Versioned, append-only history) 4 Secondary Facet Tokens auto-created: |- IDENTITY (W3C DID Core, controller, authentication) |- KEY (ML-DSA-87 / Ed25519, multibase encoding) |- PROVENANCE (Merkle leaf + root, ML-DSA-87 signature) |- COMPLIANCE (jurisdiction, framework reference) | Merkle Tree (depth 20, ~1M DIDs) | ML-DSA-87-signed root + DMRV event chain | Portable proof export (JSON-LD + JWT)
+---------------------------------------------------------+ | Merkle Registry (Depth 20) | | capacity: ~1,048,576 DID entries | | hashAlgorithm: SHA-256 | | signatureAlgorithm: ML-DSA-87 (FIPS 204) | +---------------------------------------------------------+ | | | Level 0 (Root) [ML-DSA-87-signed root hash] | | Level 1 [H(L2a + L2b)] [H(L2c + L2d)] | | Level 2 ... ... | | ... | | Level 20 (Leaves) [SHA-256(DID Doc v1)] | | [SHA-256(DID Doc v2)] | | [SHA-256(DID Doc v3)] | | ... | +---------------------------------------------------------+ | Anchoring Modes: | | - IMMEDIATE: leaf inserted + root re-signed per op | | - BATCHED: leaves queued, batch-anchored periodically | +---------------------------------------------------------+
did:aurigraph:5Hq3... |- Version 1 (created) | |- leafHash: 0xabc123... | |- merkleProof: [sibling hashes path to root] | |- rootSignature: ML-DSA-87(rootHash) | |- timestamp: 2026-04-24T10:00:00Z | |- Version 2 (key rotated) | |- leafHash: 0xdef456... | |- merkleProof: [updated sibling path] | |- rootSignature: ML-DSA-87(newRootHash) | |- timestamp: 2026-04-24T14:30:00Z | |- Version 3 (service endpoint added) | |- leafHash: 0x789abc... | |- ...
Every DID in the ledger is decomposed into 4 independently verifiable facets via the Composite Token Framework:
DID proofs can be exported in two industry-standard formats:
{ "@context": [ "https://www.w3.org/2018/credentials/v1", "https://w3id.org/security/suites/jws-2020/v1" ], "type": ["VerifiableCredential", "AurigraphDIDCredential"], "issuer": "did:aurigraph:5Hq3...", "issuanceDate": "2026-04-24T10:00:00Z", "credentialSubject": { "id": "did:aurigraph:5Hq3...", "identity": { "controller": "did:aurigraph:5Hq3...", "authentication": ["#key-1"] }, "key": { "type": "ML-DSA-87", "publicKeyMultibase": "z6Mk..." }, "provenance": { "merkleRoot": "a1b2c3...", "leafIndex": 42, "mlDsa87Signed": true }, "compliance": { "jurisdiction": "EU", "framework": "W3C-DID-CORE-V1" } }, "proof": { "type": "DataIntegrityProof", "cryptosuite": "aurigraph-ml-dsa-87-jcs-2026", "verificationMethod": "did:aurigraph:5Hq3...#key-1", "proofPurpose": "assertionMethod" } }
Compact JWT envelope for bandwidth-constrained environments (mobile, IoT):
<header: ML-DSA-87>. <payload>. <ML-DSA-87 signature bytes>
Aurigraph DID proofs can be verified on external blockchains:
AurigraphDIDVerifier.sol
aurigraph_did_verifier
Aurigraph DID Ledger | |- Proof exported as JSON-LD or JWT | +-- Ethereum Bridge | |- ABI encode(merkleRoot, leafHash, proof[], signature) | |- Call AurigraphDIDVerifier.verifyProof() | |- On-chain event: DIDVerified(did, merkleRoot, block) | +-- Solana Bridge |- Borsh serialize(merkleRoot, leafHash, proof[], signature) |- Invoke aurigraph_did_verifier::verify() |- On-chain log: DIDVerified { did, merkle_root, slot }
Every DID lifecycle event emits a DMRV attestation to the immutable audit chain:
DID_CREATED
DID_UPDATED
DID_KEY_ROTATED
DID_SERVICE_ADDED
DID_DEACTIVATED
DID_PROOF_EXPORTED
DID_BRIDGE_ANCHORED
DID Ledger Operations (/api/v11/did/ledger):
/api/v11/did/ledger
# Create a new DID with Merkle anchoring curl -X POST https://dlt.aurigraph.io/api/v11/did/ledger \ -H "Authorization: Bearer {token}" \ -d '{"did": "did:aurigraph:my-org", "didDocument": "{...}", "keyType": "ML-DSA-87", "anchorMode": "IMMEDIATE"}' # Resolve a DID (returns versioned document + 4 facets) curl https://dlt.aurigraph.io/api/v11/did/ledger/{did} # Get Merkle inclusion proof curl https://dlt.aurigraph.io/api/v11/did/ledger/{did}/proof # Verify DID integrity against Merkle root curl -X POST https://dlt.aurigraph.io/api/v11/did/ledger/{did}/verify # Get DID version history curl https://dlt.aurigraph.io/api/v11/did/ledger/{did}/history # Update DID document (creates new version) curl -X PUT https://dlt.aurigraph.io/api/v11/did/ledger/{did} \ -d '{"didDocument": "{...updated}", "reason": "key-rotation"}' # Deactivate DID curl -X DELETE https://dlt.aurigraph.io/api/v11/did/ledger/{did} # Export portable proof (JSON-LD or JWT) curl https://dlt.aurigraph.io/api/v11/did/ledger/{did}/export?format=jsonld
SDK DID Operations (/api/v11/sdk/did):
/api/v11/sdk/did
# SDK: Create DID curl -X POST https://dlt.aurigraph.io/api/v11/sdk/did \ -H "Authorization: ApiKey {appId}:{key}" \ -d '{"did": "did:aurigraph:app-001", "keyType": "ML-DSA-87", "jurisdiction": "US"}' # SDK: Resolve DID curl https://dlt.aurigraph.io/api/v11/sdk/did/{did} # SDK: Get Merkle proof curl https://dlt.aurigraph.io/api/v11/sdk/did/{did}/proof # SDK: Verify integrity curl -X POST https://dlt.aurigraph.io/api/v11/sdk/did/{did}/verify
Explore: About · Products · Features · Whitepapers · Sustainability · Tokenized carbon credits · Real-world asset tokenization · SDK · Blog · Plain-text site index · Sitemap · Contact: contact@aurigraph.io