HaasOnline’s purpose is to help more people gain control of their financial freedom as the new age of finance evolves. As a trusted partner to investors and a leading provider of financial technology, our customers look to us for the solutions they need when designing and executing on their most important trading strategies.
I’m excited to release this new awesome grid-bot script with you! It is a very powerful and dynamic grid-bot that utilizes ATR (Average True Range) for order placement, ADX (Average Directional Index) to limit when and where to trade and it offers a good bunch of settings for you to tweak it the way you like!
I hope this massive beast can generate you the income you deserve!
– – 1. Max. consecutive orders: Maximum amount of consecutive orders. Once last order is filled, stop-loss is activated
– – 2. First order size: The size of the first order. Also works as the base for next order sizes (see [Order size multiplier])
– – 3. Order size multiplier: Multiplier for how much order sizes grow, example with first order 100 and multiplier of 3; 100, 300, 900, 2700 and so on
– – 4. Take-profit %: Take-profit is calculated based on the current average entry price of open position. If your exchange doesn’t offer rebate fees, you need to take those paid fees into account!!
– – 1. Grid type: The type of grid. [ATR] type uses Average True Range, [StdDev] type uses Standard Deviation and [Fixed] type uses fixed stepping for order placement.
– – 2. Grid period length: Period length of grid. Doesn’t affect FIXED type.
– – 3. Grid base multiplier: Base multiplier, controls the distance of the orders.
– – 4. Grid fixed step: Grid fixed step defines the step size for the [FIXED] grid type.
– – 5. Grid timeframe: Interval used for grid data. Doesn’t affect FIXED type.
– – 1. ADX period length: Period length of ADX
– – 2. ADX shutdown limit: If ADX rises above this value, the bot will shutdown and exit any position it has open, using market order. Use this setting to control what volatility levels this bot should trade in. Value ignored if set to zero.
– – 3. ADX timeframe: Interval used for ADX data
– – 4. Stop-loss offset %: Stop-loss is offsetted based on the last filled entry price, NOT the current average entry price of open position
– – 5. Cooldown length (min): The length of cooldown (in minutes) after ADX-shutdown or stop-loss
“May the profits be with you…”
This topic was modified 7 months, 2 weeks ago by pshai. Reason: Limited order count
This topic was modified 7 months, 2 weeks ago by pshai.
This topic was modified 7 months, 1 week ago by pshai.
This topic was modified 6 months, 1 week ago by pshai.
This topic was modified 1 month, 1 week ago by Derrick.
Hi, I started to test your script (simulated Kraken Future Accounts with 1 BTC) and I have encounter two questions:
– I am getting the following log messages: “WARNING: No maker template available for KrakenFutures. Falling back to normal limit order.”
— Q: Do I need to create the respective maker template?
– Although the bot is showing +26% , the overall wallet amount dropped to “0.99758157” (from 1.0).
This reply was modified 7 months, 2 weeks ago by Busera.
1) With simulated accounts there are no Maker templates, so the warning is nothing to be worried about.
2) The bot reserves some assets for its orders (when it has open orders). You can add the “In Wallet” value with “In Order”/”In Use” value to get the real total (or simply stop the bot and cancel open orders).
I am running your script now exclusively for the Kraken Future Challenge, and it generates excellent results. I adjusted the settings based on 8W backtesting, which I update every week. I also use a more conservative setting to minimize the drawdown and not to maximize the return.
However, once in a while, the script gets stuck (Rather quite often), e.g., it sells only 99 of 100 contracts. In this case, I have to sell the remaining contracts manually, need to clear the statistics and restart the bot.
Are you facing the same problem?
Update: Today, during the BTC pump, all my gains were killed because the stop loss was not triggered. I am not sure why the script stops working.