Ledger, sync, offline and hardware requirements · C0924
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, not yet built
Short answer
Designed, not built: there is no code for this in the pilot. REQ-3003 says the system must 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]. Its acceptance check: attempt to transfer a token by holder is rejected; each type has chaincode tests.
This is designed, not built.
- Specification item
- REQ-3003
- 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 support mintable wallets of classes W-P, W-D, W-S, W-N, W-B, W-G with minting by quorum, identity binding, expiry and rate limits? Designed
- How many people would have to agree before a sensitive ledger action goes ahead? Designed
- What may be written to the ledger, and what is never allowed on it? Designed
See it in context: Federated ledger, spheres, tokens, wallets, bridges · Search the help center · Ask a question