reserve_locker — Group 11, Code 110

Reserve a crossover locker before the exchange flow completes.

Purpose

reserve_locker allocates the exchange-side destination state before value is finalized. Use it at the beginning of a crossover flow so the client has a deterministic place for the resulting assets.

Wire reference — authored from source

This byte layout was derived from the current raidax implementation (cmd_crossover.c). It reflects the live binary protocol used by the crossover service.

Request Body

Challenge (16 bytes) 0 Locker Key (16 bytes) 16 CC (3B) 32 Amount (8B, Big-Endian) 35 ASZ 43 Sender Address (Variable, up to 62 bytes) 44 Receipt ID (16 bytes) ... Memo (Variable length) ... 3E 3E
Field Size Description
Challenge16 bytesRandom material for request validation.
Locker Key16 bytesThe unique key for the target locker.
Currency Code3 bytesISO-style or internal currency identifier (e.g., 'BTC').
Amount8 bytesBig-endian unsigned 64-bit integer.
Address Size1 byteThe length of the following sender address (26-62).
Sender AddressVariableThe external address originating the funds.
Receipt ID16 bytesClient-generated ID for transaction tracking.
MemoVariableOptional descriptive text or metadata.