VERIFY_AUTHORITY_PROOF — Group 21, Code 4
Single-coin fallback lookup for clients that deliberately did not cache the list. Not used on the hot path.
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 II — later
This command is Phase II: convenience, recovery, or optimization that is not required for the first working move. Single-coin fallback; the cached list covers the normal path.
How it works
Normally a client answers “who is the authority for this coin?” instantly from its cached list, with no network call. This command is the deliberate fallback for the occasional case where a client did not cache the list and just needs a single coin's answer straight from the root.
The client names one coin; the root replies with the authoritative server id, the epoch, and an AES-CMAC so the answer can be trusted. It is intentionally not meant for the hot path — doing this per authentication is exactly the per-coin round trip the cached-list design was created to avoid — but it is useful for one-off checks and tooling.
Direction & encryption
- Direction: client → root
- ENC_CODE: 0 / 1
Request Body parameters
| Field | Bytes | Description |
|---|---|---|
| CH (challenge) | 16 | Standard challenge / replay protection (per header convention). |
| DN | 1 | Denomination of the coin. |
| SN | 4 | Serial number of the coin. |
| EOF | 2 | Terminator (0x3E3E). |
Response Body parameters
| Field | Bytes | Description |
|---|---|---|
| DN | 1 | Echoed denomination. |
| SN | 4 | Echoed serial number. |
| authority_id | 2 | Authoritative server id (0 = root). |
| epoch | 4 | Epoch of this answer. |
| CMAC | 16 | AES-CMAC over the answer. |