MOVE_ABORT — Group 20, Code 7
Pre-commit rollback of a MOVING_OUT coin (refused once the destination has committed).
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. Recovery: roll back a pre-commit move. Optional for v1.
How it works
A move has two phases. In the first phase the source server has only marked the coin as “moving out” but the destination has not yet taken responsibility — nothing irreversible has happened. MOVE_ABORT exists for that window: it lets the user cancel a move that has started but not yet committed, returning the coin to normal, fully-usable status on the source.
Once the destination has committed to the move (it has recorded the coin as INBOUND), abort is refused — at that point the only way “back” is a fresh move in the opposite direction. The server's reply tells the client whether the rollback succeeded or whether it was already too late.
Direction & encryption
- Direction: client → source
- ENC_CODE: 1 (coin AN)
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 |
|---|---|---|
| aborted | 1 | 1 = rolled back to AUTHORITATIVE; 0 = too late (already committed). |