MOVE_LOCKER_STATUS — Group 8, Code 91
Report the state of a move locker.
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. Part of the Phase II move-locker feature.
How it works
After setting up a move locker, the user wants to know how far along it is. This command reports the state of a move locker: still pending (waiting for the epoch), moved (the coins have arrived at the suspect and are waiting to be claimed), claimed (already collected), or failed.
The client names the destination locker; the server replies with that state, the epoch involved, and which server currently holds the coins. It only reports — it changes nothing — and can be asked of either the root or the suspect.
Direction & encryption
- Direction: client → root or suspect
- ENC_CODE: 1
Request Body parameters
| Field | Bytes | Description |
|---|---|---|
| CH (challenge) | 16 | Standard challenge / replay protection (per header convention). |
| dest_locker_id | 16 | The destination locker to query. |
| EOF | 2 | Terminator (0x3E3E). |
Response Body parameters
| Field | Bytes | Description |
|---|---|---|
| state | 1 | 0 PENDING, 1 MOVED, 2 CLAIMED, 3 FAILED. |
| effective_epoch | 4 | Epoch the move applies. |
| authority_id | 2 | Current authority server id. |