CANCEL_MOVE_LOCKER — Group 8, Code 94
Un-queue a move locker before the epoch (refused once EPOCH_MOVE_EXECUTE has run).
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
Before the epoch arrives and the move actually happens, a user can call this off. CANCEL_MOVE_LOCKER un-queues a move locker and returns the coins to normal ownership — either a regular locker or back under the user's own AN.
The user authorizes the cancellation (with the coin's secret or the locker's pickup proof). Once the epoch's server-to-server transfer has executed, it is too late to cancel here, because the coins now live on the suspect; recovering them would mean moving them back the other way. The reply states whether the cancellation succeeded.
Direction & encryption
- Direction: client → root
- ENC_CODE: 1 / pickup proof
Request Body parameters
| Field | Bytes | Description |
|---|---|---|
| CH (challenge) | 16 | Standard challenge / replay protection (per header convention). |
| dest_locker_id | 16 | The move locker to cancel. |
| EOF | 2 | Terminator (0x3E3E). |
Response Body parameters
| Field | Bytes | Description |
|---|---|---|
| cancelled | 1 | 1 = un-queued and coins returned to a normal locker / the user's AN. |