Javieralv
Gunbot Shop › Gunbot Forum › Javieralv
Forum Replies Created
-
AuthorPosts
-
Gunbot v21.9.2
– Fix pullback strategy.
– Fix SGA trend update timing.
Gunbot v22.0.7 – HFT – alpha
– Fix a candles rejection that would prevent websockets to reconnect on watchCandles.
Gunbot v22.0.6 – HFT – alpha
– Catch other undefined values/errors preventing the bot to run smooth.
– Parsing WS_SLEEP_TIME as a number.
Gunbot v22.0.5 – HFT – alpha
– Fix some undefined things that have been reported and prevent 22.0.4 to start for some users.
Gunbot v22.0.4 – HFT – alpha
– Adding binanceFutures coin-m coins, binance spot on websockets.
– Adding WS_SLEEP_TIME in GUI.
– Fix long standing bug of pnl not showing in gui without a bot restart.
Gunbot v22.0.3 – HFT – alpha
– initial broken commit of Gunbot HFT: do not use this in production
Status:
– Entire Gunbot is now migrated to pure websockets
– Only a very few initial api calls are sent with REST calls because exchanges do not send the entire history of an endpoint to websockets: they only send updates.
– So balances, candles, trades and many other endpoints MUST do their first call with REST api
– PositionRisk at binance futures is not sent via websockets (and the few informations they send are not enough for our bot)
– For this reason we need to use positionRisk with REST api call at all the times (i’m throttling it with one api call when it is needed).
– You can decide the speed of your bot: set WS_SLEEP_TIME in milliseconds in bot section of your config and play with it looking at the speed of your bot changing.
– Example i start with WS_SLEEP_TIME: 2000 and the bot is throttled with 2 seconds per pair.
– Being that you can use milliseconds, based on the ping you have to the exchange and your server performances, you can tune that down to 0 milliseconds if you are able to.
– For slower servers: use higher values up to 4/6 seconds (4000/6000)
– All pairs cycles at same time.
– It means if you have 300 pairs configured, each pair will cycle whenever a new websocket event comes in.
– Ignore all errors that you would see on console log for now.
– Strictly use this build with binanceFutures: anything else will not work.
Gunbot v22.0.2 – Patch release
Gunbot v22.0.1 – Patch release
– sga: fix case where ct sell should be allowed, but wasn’t
– Fix fetching pair lists for huobi.
– Remove irrelevant KEEP_QUOTE from futuresGrid strategy editor.
Gunbot v21.9.1
This will be the last time we are releasing Gunbot using REST api calls: by the next round, we move to full websockets for all supporting exchanges.
– Fix sell orders at Kraken.
– Fix DU count preventing smacross and other strategies to keep going even tho DU was disabled.
– Fix fibonacci.
– Fix kraken futures cycling.
– Fix an issue that would prevent stop limit to fire in futures markets.
– Fix bybit futuresGrid.
– Fix ROE showing value in futuresGrid even with no position size.
– Add additional time check to trend update logic.
Gunbot v21.9.0 – Stable preview
– Add TL_MULTIPLIER to futuresGrid (works same as in sga)
Can be used to increase or decrease the invested amount with each consecutive buy order.
Examples with trading limit 100 usdt and max buy count 3
1: each buy order is for 100 usdt
1.5: first buy 100, second buy 150, third buy 225
2: first buy 100, second buy 200, third buy 400
– Also add TL_MULTIPLIER to short side of futuresGrid
– Change futuresgrid close for bybit to “close” instead of “opposite order…”
– If you are using FTX with a subaccount, set this in config.js in ftx exchange section (same place you set api/secret)
“SUBACCOUNT”: “subaccount_name”
or it wont let you use your subaccount api keys
Gunbot v21.8.9 – Stable preview
– fix an issue that would use quote value instead of base value to open shorts at bybit.
– spotGridAdvanced: add two settings to control dca distances when TREND_LOWER_DCA is used and trend is not bullish:
TREND_GRID_MULTIPLIER & TREND_CT_MULTIPLIER
TREND_CT_MULTIPLIER: ‘Multiplier to adjust CT buy target while trend is not bullish and TREND_LOWER_DCA is used\n\nA value of 2 would double the distance, a value of 1 results in the same behavior as when TREND_LOWER_DCA is disabled’,
TREND_GRID_MULTIPLIER: ‘Multiplier to adjust the next DCA target while trend is not bullish and TREND_LOWER_DCA is used\n\nA value of 2 would double the distance, a value of 1 results in the same behavior as when TREND_LOWER_DCA is disabled’,
– Fix parameter hiding for GAIN in futuresGrid strategy editor.
Gunbot v21.8.8 – Stable preview
– Fix a case futuresGrid woudnt ever trade.
– Inject futures_gunthy tickers collection to ac.
Gunbot v21.8.7 – Stable preview
– Pushed short for futuresGrid.
DIRECTION: “LONG”
the same old futuresGrid like you know it alreadyDIRECTION: “SHORT”
lets futuresGrid trade shorts, behaves just the same as in long mode – just in a different directionDIRECTION: “AUTO”
tries to automatically determine the direction to trade, based on EMAs, OBV and ATR on 4h and 15m (independent from your strategy period). If no clear direction is detected, no new position gets opened.If you change direction while in a position in the opposite direction, futuresGrid will just continue working on that position until it closes. Next time a new position gets opened the new direction applies.
Gunbot v21.8.6 – Stable preview
– Implement LONG/SHORT positions at same time on the same pair for bybit exchange at USDT-m coins. Just use pair naming like “USDT-BTC-LONG” and “USDT-BTC-SHORT” and Gunbot will process those pairs on the same symbol, keeping trading history, orders and calculations based on the hedge mode.
– Fix an issue that would flip a position in case of limit close orders.
– Fix XDG/DOGE coin at kraken
– “sga trend”: prioritize bullish scenarios over reversal scenarios
– FuturesGrid: assume currentQty is 0 when exchange sends null.
– Fix GUI crash on pairs page in case a pair has an empty array as override value.
Gunbot v21.8.4 – Stable preview
– Update to latest beaxy coin infos values.
-
AuthorPosts
Contact us