MOVE_STATUS — Group 20, Code 8
Query the authority state of a coin on this server.
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. Diagnostic / interrupted-move recovery. Optional.
How it works
Where MOVE_QUEUE_STATUS asks the root about a pending request, MOVE_STATUS asks any server “what is your current relationship to this coin?” It is the diagnostic used to understand a move in progress or to recover from an interruption.
The answer is the coin's authority state on that server: absent (this server is not the authority — the coin is on root), authoritative (this server owns it), moving-out, moved-out (handed to another server, with which one), or inbound (just received, awaiting its new secret). A client can poll the servers involved to figure out exactly where a half-finished move stopped and what step to retry.
Direction & encryption
- Direction: client → any server
- ENC_CODE: 0 / 1
Request Body parameters
| Field | Bytes | Description |
|---|---|---|
| CH (challenge) | 16 | Standard challenge / replay protection (per header convention). |
| DN | 1 | Denomination of coin X. |
| SN | 4 | Serial number of coin X. |
| EOF | 2 | Terminator (0x3E3E). |
Response Body parameters
| Field | Bytes | Description |
|---|---|---|
| state | 1 | 0 ABSENT (on root), 1 AUTHORITATIVE, 2 MOVING_OUT, 3 MOVED_OUT, 4 INBOUND. |
| target_id | 2 | For MOVING/MOVED_OUT: destination server id. |
| epoch | 4 | Epoch of the current authority record. |