CLAIM_MOVE_LOCKER — Group 8, Code 92
After the epoch, pick up the moved coin from the suspect and re-POWN to a private AN.
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
This is how the user collects coins that were moved to a suspect via a move locker. After the epoch has executed the move, the coins sit in a destination locker on the suspect, held under a temporary locker key rather than a normal owner secret. CLAIM_MOVE_LOCKER lets the rightful user take final ownership.
The user proves they hold the secret pickup code committed when the locker was created (a challenge-response, so the proof cannot be replayed), and supplies a fresh new Authenticity Number for each coin. The suspect verifies the proof and re-keys each coin to the user's new private AN, completing the move. From this point the coin is fully owned by the user on the suspect. This mirrors how a trade-locker purchase already re-keys coins to a buyer once a condition is met.
Direction & encryption
- Direction: client → suspect
- ENC_CODE: bootstrap (pickup code)
Request Body parameters
| Field | Bytes | Description |
|---|---|---|
| dest_locker_id | 16 | The destination locker to claim. |
| pickup_proof | 16 | Proof of the pickup secret (challenge-response, no replay). |
| count | 2 | Number of coins. |
| new_AN | var | Repeating: 16-byte fresh AN per coin. |
| EOF | 2 | Terminator (0x3E3E). |
Response Body parameters
| Field | Bytes | Description |
|---|---|---|
| claimed | 2 | Number of coins claimed and re-keyed. |