Ledger, sync, offline and hardware requirements · C0922
What may be written to the ledger, and what is never allowed on it?
Designed, not yet built
Short answer
No. The specification describes it, but the pilot does not include it. For reference, REQ-3001 (a top-priority requirement, all three tiers) says the ledger must store only: salted record commitments, consent tokens and metadata, audit batch roots, authority/transfer records, wallet and token state, node presence, alerts and tombstones. Patient content, names, national ids and raw clinical values must never be written. Check: a schema linter and a runtime chaincode check reject any field not on the allow-list; a red-team test injecting a name/CPF is refused.
This is designed, not built.
- Specification item
- REQ-3001
- 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
- What is a sphere, and how does a clinic or network fit in one? Designed
- Does AuroraMed implement the token types ID, ROLE, CONS, GRANT, XFER, BRG-A/BRG-B, NODE, ALERT, BG and DELEG with the semantics in design 11.5, all non-transferable except through protocol operations. [Recommended: types from design 11.5; owner must confirm the final list]? Designed
See it in context: Federated ledger, spheres, tokens, wallets, bridges · Search the help center · Ask a question