Ledger, sync, offline and hardware requirements · C0925
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, not yet built
Short answer
REQ-3004 is a top-priority requirement for all three tiers: the system must 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. This is on the design side of the line. Nothing in v0.2.0 does it. To verify it, the specification says mass-mint above threshold raises a Red alert and freezes minting.
This is designed, not built.
- Specification item
- REQ-3004
- 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
- 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
- How many people would have to agree before a sensitive ledger action goes ahead? Designed
- How would two spheres be connected through a bridge? Designed
- What is a sphere, and how does a clinic or network fit in one? Designed
See it in context: Federated ledger, spheres, tokens, wallets, bridges · Search the help center · Ask a question