Ledger, sync, offline and hardware requirements · C0930
How are record fingerprints on the ledger prevented from revealing anything?
Designed, not yet built
Short answer
No. The specification describes it, but the pilot does not include it. REQ-3009 says record commitments must be H(salt‖digest) with per-record 128-bit+ random salts held off-ledger. Its acceptance check: dictionary attack test on low-entropy values fails without salt.
This is designed, not built.
- Specification item
- REQ-3009
- Specification priority
- P0 (of P0 to P3)
- Tiers
- Small, 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 is a patient's consent signed and revoked on the ledger? Designed
- How are patient pseudonyms built, and how can they be cut? Designed
- How would cryptographic erasure of a patient's data work? Designed
- Would typing rhythm or location be used to judge a session's risk? Designed
See it in context: Federated ledger, spheres, tokens, wallets, bridges · Search the help center · Ask a question