Ledger, sync, offline and hardware requirements · C0966
Which encryption would transfers use?
Designed, not yet built
Short answer
How would it be tested? The specification says handshake test shows hybrid group negotiated. That is the check for REQ-3402: the transfer must use AES-256-GCM or ChaCha20-Poly1305 for data and hybrid X25519 + ML-KEM for key exchange. Not yet. It is designed in the specification and not built in the pilot.
This is designed, not built.
- Specification item
- REQ-3402
- Specification priority
- P0 (of P0 to P3)
- Tiers
- Medium, Large
Status as of September 30, 2026. Version 0.2.0, synthetic data only. See what's built today. Not legal, medical or security advice.
Related answers
- How would server-to-server clinical transfers be protected? Designed
- Does AuroraMed document that decoys provide traffic-analysis resistance and not confidentiality or quantum resistance? Designed
- Who authorizes a transfer before data leaves? Designed
See it in context: Server-to-server transfer, three streams · Search the help center · Ask a question