PUSH_AUTHORITY_SNAPSHOT — Group 21, Code 10
Root publishes a new snapshot + delta to a trusted mirror.
Design-stage — parameters are a first draft
Field sizes are drafted from raidax/ideas_for_suspect_raida_servers.txt (Addenda 5–7) and are not final or implementation-verified. The body is encrypted per the header ENC_CODE; see below.
Phase I — essential
This command is part of the Phase I minimum needed for a coin to move from root to suspect (and back) and be trusted by a workstation. Gets the list onto mirrors so clients can fetch it.
How it works
This is a server-to-server publishing command, not something a user calls. At each epoch the root produces the new authority list (and the delta from last epoch) and pushes it out to the trusted mirror servers that will serve it to clients.
The payload is signed with the root's AES-CMAC, so a mirror stores and redistributes the exact bytes the root produced and cannot alter them. Mirrors exist so that the millions of client downloads are spread across many servers for availability; the root remains the single author of the truth. The mirror replies that it stored the snapshot.
Direction & encryption
- Direction: root → mirror
- ENC_CODE: 7 (K_rs)
Request Body parameters
| Field | Bytes | Description |
|---|---|---|
| epoch | 4 | Epoch id being published. |
| full | var | Full snapshot bytes (count + entries). |
| delta | var | Delta bytes from the previous epoch. |
| CMAC | 16 | Root's AES-CMAC over (epoch || full || delta). |
Response Body parameters
| Field | Bytes | Description |
|---|---|---|
| stored | 1 | 1 = mirror accepted and stored the snapshot. |