Messages
{
"id": "replace-43",
"method": "wallet.execute_replace_by_slot_packed",
"payload": {
"header": {
"accountId": "123",
"market": "0x8121ee960066e4344a213f9ac7502395502aee7a",
"authNonce": "1",
"nonce": "1720000000123",
"deadline": "1720000030",
"clientOrderId": "0x0000000000000000000000000000000000000000000000000000000000000001",
"builder": "0x0000000000000000000000000000000000000000",
"builderFeePps": "0"
},
"packedOps": "0x<one-or-more-32-byte-words>",
"expectedOrderIds": [
"31"
],
"signature": "0x..."
},
"authorization7702": null
}WebSocket methods
Execute packed slot replacement
Submit compact maker-slot operations over the Relay WebSocket.
WSS
/
relay
/
ws
Send
wallet.execute_replace_by_slot_packed with a connection-local id. The payload follows the REST packed-operation contract.
The same planning-time slot-binding rules apply over WebSocket: 0 requires an empty slot, a specific ID requires that exact order, and 18446744073709551615 is the wildcard for whichever order currently occupies the slot. Relay does not wait for finalization during planning, and signer ordering does not make concurrent planning observe preceding transactions. For continuous replacement, use the wildcard when that is the intended behavior; exact IDs require observing the corresponding proposed state first.Messages
{
"id": "replace-43",
"method": "wallet.execute_replace_by_slot_packed",
"payload": {
"header": {
"accountId": "123",
"market": "0x8121ee960066e4344a213f9ac7502395502aee7a",
"authNonce": "1",
"nonce": "1720000000123",
"deadline": "1720000030",
"clientOrderId": "0x0000000000000000000000000000000000000000000000000000000000000001",
"builder": "0x0000000000000000000000000000000000000000",
"builderFeePps": "0"
},
"packedOps": "0x<one-or-more-32-byte-words>",
"expectedOrderIds": [
"31"
],
"signature": "0x..."
},
"authorization7702": null
}bearerAuth
type:http
Wallet-bound JWT supplied in the WebSocket upgrade Authorization header.
wallet.execute_replace_by_slot_packed