After an initial fill, the “Futures Scalper” will place a new buy order below that price and a new sell order above that price. New orders that add to the established position are placed at the scalp interval, while new orders with position-closing effect are placed at the profit interval. Users can choose between two different modes of booking orders: either persistent order mode (which can allow multiple orders to become laddered in the book for better queue position) or non-persistent order mode (which will never book more than one order above and/or one order below the current price). An optional user-configurable smoothing parameter allows the algo to compute a “true price” point in realtime. This “true price” involves a double-weighting of both volume-at-price and time-at-price. This feature can enhance the profitability of transient, small-scale deviations away from the “true price” by dynamically expanding the profit interval at appropriate times.
The “Futures Scalper” job also contains logic to widen out intervals by a user-defined multiplier in the case of increased volatility. By allowing the user to set a “move duration” and a “move size” for each contract, the job will automatically apply a multiplier if the future moves greater than the “move size” within the specified “move duration”. The job’s parameters will return to their normal state once the market returns to normal conditions.
Please contact the developer at email@example.com with any questions you might have regarding technicalities, client use cases, etc.
All of the variables below can be configured or modified at runtime. This gives users the power to modify their job behavior throughout the day without having to make code changes.
|smoothing_window||int||45||in seconds (2-100), or 0=disabled|
|onPriceLimitsExceeded||int||0||0=work one-sided market only, 1=close out position and deactivate row|
|remainingPositionOnRowDeactivation||int||0||0=leave as-is, 1=close out position|
|algoBias||int||2||0=auto, 1=aggressive, 2=normal, 3=conservative|
|grid_name||string||the main grid will be named ‘scalpers_[grid_name]’|
|verbosity||int||1||log verbosity: 1=normal, 2=detailed, 3=extended|
|persistentOrderDensityControl||int||0||0=off, 1=opening side only, 2=opening and closing sides|
More About Exegy
St. Louis, MO — October 31, 2023 – Exegy, the global leader in intelligent market data, advanced trading, and execution systems, today announces the appointment of industry veteran Brian Pomraning…
Introducing a purpose-built solution to handle the complexity of FIX while dramatically improving performance St. Louis, New York, Paris – October 26, 2023 – Exegy, a leading developer of high-performance…
nxFramework FIX engine offers scalable way to handle large volumes of FIX traffic while reducing server footprint The FIX® Protocol is a market standard for electronic messaging, facilitating the exchange…