protectionTicks ticks against you on the
ladder, and never above what the
contract can pay. protectionTicks is published in
GET /v1/config;"ioc": true, below), so it takes what is
resting up to that price and the remainder expires at once, without resting.
Its signed expiresAt is about two seconds ahead, because the contract never
fills an order after its signed expiry.expiresAt, and rests until then if it is
not filled first."ioc": true beside the order (not inside it:
it is not part of what you sign). The order matches once against the book in
front of it and the remainder expires within the same step, so it never rests,
and it does not count against your account's
resting order cap. Its expiresAt must still be in
the future when the order is sequenced, since the contract checks every fill
against the expiry you signed: a few seconds ahead of your clock is enough. The
web client sends every market order this way. Over FIX, 59=3 with 126.OPEN_ORDER_LIMIT) and the books it holds orders or
positions in (BOOK_LIMIT). An order past either cap is refused whole, before
it matches. The caps decide no price, fee or priority.