Ledger, sync, offline and hardware requirements · C0944
Does AuroraMed pad bundle sizes and add batching jitter as a limited traffic-analysis countermeasure?
Designed, not yet built
Short answer
How would it be tested? The specification says observed bundle sizes fall into padding classes. That is the check for REQ-3108: the system must pad bundle sizes and add batching jitter as a limited traffic-analysis countermeasure. This is on the design side of the line. Nothing in v0.2.0 does it.
This is designed, not built.
- Specification item
- REQ-3108
- Specification priority
- P2 (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
- Who has to approve resuming sync after a pause? Designed
- How are backups tiered, and what makes them tamper-evident? Designed
- How would a restored backup be checked before going live? Designed
- Does a detected integrity problem also pause sync? Designed
See it in context: Sync, backup, read limiter and safe degradation · Search the help center · Ask a question