Set Slot Boundaries for Trade Execution
maxSlot and minSlot add execution constraints to trade requests.
ZeroSlip adds maxSlot and minSlot to Trade API requests. These parameters define slot boundaries for execution: a transaction fails if it lands after the maximum slot or before the minimum slot.
For applications responding to a streamed event, maxSlot provides a way to reject a trade that reaches the network too late for the intended window. minSlot provides the corresponding lower boundary.
A rejected transaction can still incur network and priority fees. These settings constrain when a transaction may execute; they do not guarantee that it will land inside the window. Read the Trade API documentation for the parameters.