DHT: Design storage schema for identity documents #1
Description
Context
Identity documents need distributed storage across DHT nodes for redundancy and censorship resistance. This is part of the core SID requirement: "Storage: Encrypted and distributed across a DHT (Distributed Hash Table)".
Scope
- Define DHT key format for identity lookups (DID-based)
- Design encrypted document format (structure, metadata)
- Specify replication strategy (minimum 3 nodes)
- Define versioning scheme for identity updates
- Document storage/retrieval flow diagrams
Dependencies
None - this is the first step in DHT identity storage
Acceptance Criteria
- Document specifying DHT key derivation from DID
- Encrypted document schema (JSON/binary format)
- Replication strategy documented (node selection, quorum)
- Version control mechanism defined
- Flow diagrams for store/retrieve operations
- Security analysis (encryption at rest, key management)
- Reviewed and approved by team
Technical Notes
- Consider using DID as DHT key hash input
- Encryption must use ChaCha20-Poly1305 (consistent with lib-identity)
- Plan for future support of document rotation/updates
- Reference existing code: lib-identity has QuantumWallet and backup encryption already using ChaCha20-Poly1305