Ledger, sync, offline and hardware requirements · C0929
How is a patient's consent signed and revoked on the ledger?
Designed, not yet built
Short answer
Consent tokens must be signed by the patient wallet (or delegate) over canonical bytes including the hash of the rendered text and must be revocable with immediate ledger effect. That is REQ-3008, a top-priority requirement for all three tiers. This is on the design side of the line. Nothing in v0.2.0 does it. Test in the specification: revocation blocks new access within the propagation target [Open seconds]; signature verification fails if text hash mismatched. Parts of it are explicitly marked as open in the specification.
This is designed, not built.
- Specification item
- REQ-3008
- 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
- Would typing rhythm or location be used to judge a session's risk? Designed
- How are record fingerprints on the ledger prevented from revealing anything? Designed
- How are patient pseudonyms built, and how can they be cut? Designed
- How would two spheres be connected through a bridge? Designed
See it in context: Federated ledger, spheres, tokens, wallets, bridges · Search the help center · Ask a question