Ledger, sync, offline and hardware requirements · C0927
How would two spheres be connected through a bridge?
Designed, not yet built
Short answer
How would it be tested? The specification says fault-injection tests: kill relayer mid-commit leaves state IN_DOUBT then resolved; token count per bridge always 2. That is the check for REQ-3006: bridges between spheres must use exactly two mirrored bridge tokens with history on both sides, two-phase commit with time locks and defined failure states. Not yet. It is designed in the specification and not built in the pilot.
This is designed, not built.
- Specification item
- REQ-3006
- Specification priority
- P0 (of P0 to P3)
- Tiers
- 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 many people would have to agree before a sensitive ledger action goes ahead? Designed
- Would typing rhythm or location be used to judge a session's risk? Designed
- How is a patient's consent signed and revoked on the ledger? 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
See it in context: Federated ledger, spheres, tokens, wallets, bridges · Search the help center · Ask a question