(T - 2 days, T + 1 day), where T is the unix millisecond timestamp on the block of the transaction.
Notes for API traders
- For each batch of orders or cancels, fetch and increment an atomic counter that ensures a unique nonce for the address. The atomic counter can be fast-forwarded to current unix milliseconds if needed.
- For concurrent operations, we recommend using an shared atomic nonce counter ensuring unique nonces per transaction/api call.
- For batch operations, like place/cancel orders, there’s a hard cap of 100 ops per batch per api call.